Programmable synchronization structure with auxiliary data link

ABSTRACT

A method is provided for creating an auxiliary link embedded in the overhead structure of a primary data link. The primary data link is organized in a frame structure which includes data sections and header sections. Information in the header sections is used to synchronize and capture transmitted messages. However, not all the overhead bits need be used for synchronization. Bits may be selectively “robbed” from the header section and used to transfer information in an auxiliary data link. The number of bits that are used to support the auxiliary data link, as well as the placement of these bits in the header section are both selectable. An apparatus, specifically the AMCC  3062  Performance Monitor IC, has also been described which supports the establishment of an auxiliary data link in accordance with the above-mentioned method.

BACKGROUND OF THE INVENTION

This invention relates generally to communication circuitry and, more particularly, to a system and method of embedding an auxiliary communication link in the overhead structure of a primary communication link.

Auxiliary communication links are often necessary for the maintenance and support of a primary communication link. To that end, a second data link must be established in parallel to the primary data link. For example, an auxiliary telephone line for use in maintenance of the telephone system.

In SONET/SDH communications bytes are reserved in the line overhead section of the frame structure. Many telecommunication users have the expertise to easily construct an auxiliary data link based in the SONET/SDH frame structure. However, the fiber optic technician does not always have access to SONET/SDH messages they pass. Alternately, many fiber optic cable technicians establish a separate redundant line for maintenance communications.

Communication protocols, such as SONET and SDH, typically rely on a fixed header structure to align and synchronize the communications frame structure. While it is critical to operate in accordance with known procedures, there are circumstances when the use of a rigid header structure is detrimental to communications. For example, in a high bit error rate environment, a larger number of bits in the header increases the probability that loss of sync and loss of frame errors will be generated.

It would be advantageous if an auxiliary data link could be established in a communications system without using bytes originally intended for the primary data link.

It would be advantageous if the number and the placement of bits used for synchronization of the data frame structure could be made more flexible, or controllable by the system users.

It would be advantageous if the auxiliary data link could be formed from the overhead structure in the primary data link.

It would be advantageous if the allocation of bytes made for the auxiliary data could be made variable to account for dynamic circumstances, so that the number of auxiliary data bytes could be reduced when more bytes are needed for overhead management, and the number of auxiliary data bits could be increased when a critical auxiliary link message needs to be communicated.

It would be advantageous if the relative location of the auxiliary data link in the overhead section of the primary link could be moved for convenience in communications between system repeaters.

It would be advantageous if the number of bits used for synchronization of the frame structure could be made variable. It would be advantageous if the number of header bits checked to acquire a frame could be made larger than the number of header bits checked for loss of synchronization.

SUMMARY OF THE INVENTION

Accordingly, a method for generating an auxiliary communication link is provided. The method comprising:

receiving a first stream of information;

organizing the information into a frame structure which includes a selectable group of overhead bits for synchronization of the frame, and a selectable group of overhead bits to communicate an auxiliary message;

selecting the group of synchronization bits to read;

in response to reading the group of synchronization overhead bits, synchronizing the information into the frame structure;

selecting the group of auxiliary message overhead bits; and

in response to reading the auxiliary message group of overhead bits, recovering an auxiliary message.

The synchronization of the received information into the frame structure includes:

organizing the received information into a block with a header section having a plurality of m bits and a data section;

reading the group of synchronization overhead bits from the header section; and

in which the recovery of the auxiliary message includes reading the group of auxiliary message bits in the header section.

The selection of the group of synchronization overhead bits includes selecting between zero to m bits (all the bits in the header section). The part of the header section not used by the synchronization bits is used for the auxiliary data. Further, the selection of the group of auxiliary message overhead bits includes selecting the location of these bits in the header section.

The method further comprising:

providing a new auxiliary message for transmission;

organizing transmit information into the frame structure including a block with a header section and a data section;

writing the new auxiliary message in the header section of the transmit information; and

transmitting the information.

As in the receiving process, the method comprising:

selecting a group of overhead bits for the synchronization of the transmit information, and a group of overhead bits to communicate the new auxiliary message; and

writing both groups of overhead bits into the header section of the transmit information.

In some aspects of the invention the new auxiliary message is simply the original auxiliary being passed through. Although the same number of header bits must be used to pass the auxiliary message, the location of these bits in the header section may be changed between the reception and transmission of the auxiliary message.

An integrated circuit (IC) transmission repeater with auxiliary data link is also provided. The repeater comprises a decoder to receive information including an auxiliary message written in a second group of selectable overhead bits. The decoder reads a first group of selectable overhead bits to synchronize the received information into a frame structure including a block with a data section and a header section. The decoder has inputs to select the first and second group of overhead bits, and an output to provide the auxiliary message recovered from reading the second group of overhead bits.

As described in the method, the header section has a plurality of m bits, although the header may also be one byte, or less. The decoder reads the first and second group of overhead bits from the header section.

In some aspects of the invention a deinterleaver circuit accepts the received information before the decoder circuit. The deinterleaver has n outputs to provide the received information deinterleaved into n parallel data streams. Then, the decoder accepts the n parallel data streams from the deinterleaver circuit. The decoder reads the first group of overhead bits from the n parallel header sections to synchronize the received information, and reads the second group of overhead bits from n parallel header sections to recover the auxiliary message.

The decoder accepts commands to select the number of second group overhead bits for each of the header sections of the n parallel data streams. Further, the decoder accepts commands for the location of the second group of overhead bits in each of the n header sections.

An encoder accepts a new auxiliary message, and organizes transmit information into the above-mentioned frame structure. The encoder supplies the new auxiliary message written in a fourth group of overhead bits of the header section. The encoder also selects a third group of overhead bits for synchronization of the transmit information. The encoder writes the third group of overhead bits in the header section.

In some aspects of the invention the encoder provides n parallel data streams organized in the frame structure including n blocks having header and data sections. The encoder accepts commands to select the number and location of the fourth group overhead bits in each of the n header sections. An interleaver, connected to the plurality of n encoder outputs, interleaves the n parallel data streams to form the transmit information at the interleaver output.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary network including a performance monitoring device of the present invention.

FIG. 2 depicts the performance monitor device of FIG. 1, performing an exemplary monitoring function.

FIG. 3 is a schematic block diagram illustrating the basic blocks of the S3062.

FIGS. 4a and 4 b are detailed schematic block diagrams illustrating the present invention of FIG. 3.

FIG. 5 illustrates the FEC encoded data structure of the present invention.

FIG. 6 illustrates the frame check enabling.

FIG. 7 depicts the FEC framing state machine.

FIG. 8 depicts an exemplary first frame structure.

FIG. 9 illustrates an exemplary interleaved frame structure.

FIG. 10 is a schematic block diagram of a system for auxiliary communications.

FIGS. 11a and 11 b are flowcharts illustrating a method for generating an auxiliary communication link.

FIG. 12 is a schematic block diagram illustrating the clocking associated with FEC.

FIG. 13 is a schematic block diagram illustrating details of he GBE monitor.

FIG. 14 is a logic diagram depicting the determination of a running disparity (RD) error.

FIGS. 15 and 16 depict exemplary SONET frame structures, including the locations of the transport overhead bytes within the SONET/SDH frame.

FIG. 17 is a logic diagram illustrating the operation of the LOS/OOF state machine.

FIG. 18 illustrates the Micro Present Byte control MUX.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The principles of the present invention auxiliary data link have been specifically embodied in an integrated circuit (IC), namely, the AMCC S3062 Performance Monitor. Aspects of the invention are demonstrated using the S3062 as an example. However, the present invention is not necessarily limited to any particular embodiments implemented in this IC.

The S3062 Multi-Rate SONET/SDH STS-3/STM-1, STS-12/STM-4, STS-48/STM-16 & Gigabit Ethernet (GBE) Performance Monitor chip is a fully integrated checking device complying with SONET/SDH transmission standards. The S3062 implements all necessary performance monitoring functions on the SONET/SDH section and line overhead bytes at three different rates (STS-3/STM-1, STS-12/STM-4, and STS-48/STM-16). It also has a mode of operation permitting it to monitor a Gigabit Ethernet data stream for loss of synchronization, 8B/10B code violations and disparity errors. Furthermore, any type of data entering and leaving the chip can be optionally decoded and encoded with forward error correction (FEC) information and also differentially encoded and decoded.

FIG. 11 illustrates an exemplary network 10 including a performance monitoring device 12 of the present invention. Data is received from an optic fiber and passed through a clock/data recovery device (CDR) 14 and a demultiplexer device 16 to the S3062. The S3062 (12), optionally, carries out performance monitor error checking, and overhead data extraction, and insertion. Detected errors and accumulated error counts can be accessed by the user either through a processor interface, an FPGA interface, or in a number of cases, from I/O pins (not explicitly shown). The data stream is then transmitted out onto the fiber via a high-speed multiplexer 18, and an optics device 20. All SONET/GBE performance monitor error checking and overhead insertion may be by-passed by selecting the low-power pass-through mode of operation.

FIG. 2 depicts the performance monitor device of FIG. 1, performing an exemplary monitoring function. The S3062 (12) is being used to monitor data, without inserting overhead. In this application, the MUX 18 may be removed and a Port By-Pass circuit 22 added for a low power monitoring solution.

The S3062 is used, but not necessarily limited to use in the following applications:

1) SONET/SDH-based transmission systems and test equipment;

2) Gigabit Ethernet-based transmission systems;

3) Add Drop Multiplexers (ADM);

4) Fiber optic terminators, repeaters and test equipment; and

5) FEC augmented applications for reliable data transmission over impaired channels.

The following is a list of S3062 features which are explained in greater detail, below:

1) Provides a 16 bit input and a 16 bit output single-ended positive emitter-coupled logic (PECL) data path;

2) Optionally differentially decodes and encodes incoming and outgoing data;

3) Provides optional Reed Solomon (RS) encoding of data for Forward Error Correction (FEC);

4) Provides optional Reed Solomon decoding of data for Forward Error Correction (FEC);

5) Provides on-chip clock dividers to simplify external clock generation for Forward Error Correction (FEC);

6) Optionally provides a data link in the FEC framing bytes for transmission of messages, error information, orderwire, etc.;

7) Provides selectable error correcting rates;

8) Monitors FEC data for total corrected bit errors, corrected ones, corrected zeros, corrected bytes, and uncorrectable blocks;

9) Extracts and optionally inserts SONET/SDH overhead bytes via a microprocessor port;

10) Extracts and optionally inserts SONET/SDH overhead bytes via a FPGA port;

11) Extracts and optionally inserts orderwire bytes (E1 and E2) via serial I/O;

12) Extracts and optionally inserts the data communication channels (D1-3 and D4-12) via serial I/O;

13) Performs frame and byte alignment and outputs frame pulses;

14) Performs optional frame-synchronous scrambling and descrambling;

15) Monitors for Loss of Signal and outputs alarm (LOS);

16) Monitors for Out of Frame and outputs alarm (OOF);

17) Monitors for Loss of Frame and outputs alarm (LOF);

18) Monitors J0 byte for section trace messages;

19) Monitors B1 byte for Bit Interleave parity errors and outputs error indications (B1ERR);

20) Monitors B2 byte for Bit interleave parity errors, Signal Degrade (SD) and Signal Fail (SF);

21) Monitors K1, K2 bytes for Automatic Protection Switching (APS) changes, line AIS and line RDI;

22) Monitors the S1 byte for mismatches and inconsistent values;

23) Monitors the M1 byte for Remote Error Indications (REI);

24) Monitors for Gigabit Ethernet Loss of Synchronization (LOS), 8B/10B code violations and disparity errors;

25) Optionally calculates and inserts section bit interleaved parity (B1);

26) Optionally calculates and inserts line bit interleaved parity (B2);

27) Optionally turns OFF (sets low) all transmitted data;

28) Optionally inserts AIS, either automatically depending on line conditions or under user control;

29) Optionally inserts valid SONET/SDH section and line overhead on any data format with a CLKINP/N and TXCLKP/N input;

30) Generates valid SONET/SDH section (regenerator) overhead with line AIS data with only a TXCLKP/N input;

31) Optionally permits transparent pass through of all data regardless of format; and

32) Optionally injects bit errors in any data type.

Pass Through and FEC Overview

FIG. 3 is a schematic block diagram illustrating the basic blocks of the S3062. The S3062 Performance Monitor 12 optionally performs forward error correction (FEC) on any data format. If the data is in SONET/SDH format, the S3062 implements all required features to check the data stream and allow for the extraction and insertion of the section and line overhead bytes. It also implements Gigabit Ethernet 8B/10B monitoring of the data stream. The data stream may run at any frequency from 155.52 to 2500 Mb/s without FEC, which includes STS-3/STM-1, STS-12/STM-4, STS-48/STM-16 and Gigabit Ethernet rates. All modes use a 16-bit parallel single-ended low voltage positive emitter-coupled logic (LVPECL) data path. The S3062 implements forward error correction, SONET/SDH section and line overhead monitoring and insertion, and Gigabit Ethernet monitoring.

As shown in FIG. 3, data of any type may be passed through this chip without SONET/SDH or Gigabit Ethernet monitoring. In this pass-through mode of operation the performance monitors are turned OFF to reduce power consumption. The differential and FEC encoder/decoder may also be turned OFF to further reduce the S3062's power consumption.

The FEC function is implemented with a variable-rate Reed Solomon codec based upon the Galois Field (2⁸) symbols. Code rate and error correcting capability are selectable from rate=238/255, 8 byte errors correctable, to rate=248/255, 3 byte correctable. Error statistics are collected for a variety of conditions including total corrected bit errors, corrected ones, corrected zeros and uncorrectable blocks. The codec implementation encompasses the ITU G.975 recommendation for codec and rate, interleaved to four levels. A programmable frame synchronization byte is inserted for rapid and reliable acquisition of the coding frame boundary.

Gigabit Ethernet Overview

The Gigabit Ethernet circuitry 30 (FIG. 3) monitors the received data stream for: loss of synchronization; 8B/10B code violations; and disparity errors. These errors are flagged and available at the I/O signal pins. Error counts are also accumulated over 1 second periods and are available via the processor interface.

Sonet/SDH Overview

In SONET/SDH mode, all received section and line overhead bytes are captured and placed in a memory in SONET monitor 32 (FIG. 3). The memory is accessible from either a processor or an FPGA. The overhead bytes that are defined by the SONET/SDH standards are also monitored for errors and performance monitoring (PM) statistics. The results are accessible from the processor or FPGA interface. In addition to being stored in an accessible memory, received section overhead is managed as follows:

1) A1 and A2 bytes are checked for framing and byte alignment;

2) J0 byte is monitored for section trace messages;

3) B1 byte is monitored for bit interleaved parity errors, which are accumulated over 1 second periods;

4) E1 byte is optionally serialized and output on an I/O pin;

5) D1-3 bytes are optionally serialized and output on an I/O pin; and

6) Data can be descrambled in accordance with SONET/SDH standards. Section errors—LOS, LOF, OOF and B1—are output on I/O pins and are available to the processor and FPGA interfaces.

In addition to being stored in an accessible memory, received line overhead is managed as follows:

1) B2 byte is monitored for bit interleaved parity errors, which are accumulated over 1 second periods;

2) K1 and K2 bytes are monitored for new or inconsistent values. K2 is also monitored for line AIS and RDI;

3) D4-12 bytes are optionally serialized and output on an I/O pin;

4) S1 byte is monitored for inconsistent values and for mismatches with a software programmable value;

5) M1 byte is monitored for REI errors, which are accumulated over 1 second periods; and

6) E2 byte is optionally serialized and output on an I/O pin. Line error indicators—line AIS, line RDI, line REI, B2, signal fail, signal degrade, K1, K2 and S1 changes are only accessible via the processor or FPGA interfaces, they are not output on I/O pins.

All transmitted section and line overhead bytes can be written through the FPGA or processor interface. In addition, data transmission can be modified as follows:

1) Framing bytes can be regenerated with values A1=F6h and A2=28h;

2) J0 byte may be filled with section trace bytes from a memory;

3) B1 and B2 bytes can be recalculated;

4) E1, D1-3, D4-12 and E2 bytes can be sourced, serially from S3062 I/O pins;

5) data can be scrambled in accordance with SONET/SDH standards;

6) line AIS can be activated automatically when LOS or LOF conditions are detected, or the user may force the transmitter to output line AIS; and

7) the entire data stream can be turned off (all zeros output).

The SONET/SDH application is designed to monitor incoming SONET/SDH data streams and optionally modify them. It can also be used as a SONET/SDH generator. The S3062 transmit clock (TXCLKP/N) will generate correct section (regenerator) overhead and line AIS if the receive clock (CLKINP/N) is absent. If the receive clock is present, any data format may be turned into SONET/SDH frame. The frame counter does not need to find byte alignment to begin running.

Pass-Through and FEC

FIGS. 4a and 4 b are detailed schematic block diagrams illustrating the present invention of FIG. 3. The received data enters the chip 12 on line 50 and is demultiplexed, or deinterleaved, by deMUX 52, from 16-bits to 32-bits. The data goes to the decoder, or decode block 54, if the received stream of information has been differentially or FEC encoded. Otherwise, it bypasses the decode block 54 and travels to the re-synchronizing FIFO 56. The data stream may optionally be differentially encoded and decoded if the data outside the S3062 (12) is inverted an unknown number of times. Regardless of the number of inversions, the differential decoder function will always output the exact data that was received by the encoder.

In decoder 54, data may pass from the differential decoder function to the FEC decoder function. The decoder 54 locates the FEC byte boundaries by aligning to the Frame Synchronization Byte (FSB). The default value for this byte is 3Ch, but it is reprogrammable through the ‘FSB’ register. A FSB is sent as the first byte of a 255-byte block. The blocks are interleaved such that 4 FSBs will be received one after the other followed by the rest of the four interleaved 255-byte blocks.

FIG. 5 illustrates the FEC encoded data structure of the present invention. The decoder 54 synchronizes to the four FSBs, going in-frame after receiving 2 consecutive groups, spaced the correct distance apart (4*255 bytes). By default, all of the bits in the 4-FSB group are checked. If some of the FSB bits are being robbed for a data link, as explained in detail below, software can program the S3062 to only check the remaining real FSB bits for the framing value.

After frame has been found, the framer keeps looking for the 4-FSB groups at the correct spacing. It goes out of sync after seeing 4 consecutive bad groups. To make the algorithm more robust to bit errors, by default only the 6 most and 6 least significant bits in the 4-byte group are checked once the framer is in-frame. For example, in FIG. 5 above, the bits checked would be the 6 most significant bits of FSB1 and the 6 least significant bits of FSB4. The default condition can be changed by software.

The defaults, used in the framing algorithm, are selectable as follows:

The number of consecutive error-free groups required to go in-frame, default 2, can be changed to any value from 0-15. If the value 0 is selected, framing will not occur correctly; The bits within the 4-FSB group to check when out-of-frame can be changed by writing to the ‘FEC Out-of-Frame FSB Check Enable’ register. The default register value is FFFF FFFFh, check all bits. If too few bits are selected, framing will not occur correctly;

The number of consecutive erred groups required to go out-of-frame, default 4, can be changed to any value from 0-15. If the value 0 is selected, framing will not occur correctly;

FIG. 6 illustrates the frame check enabling. Which bits within the 4-FSB group to check when in-frame can be changed by writing to the ‘FEC In-Frame FSB Check Enable’ register. The default register value is fc00 003fh, check 12 bits. If too few bits are selected, framing will not occur correctly. If too many bits are selected, the framer will be more likely to go out-of-frame when the bit error rate is high. The frame check enable registers work as follows: each bit in the 32-bit register represents a bit in the 4-FSB group. If the enable for a particular bit is on (1), the bit will be checked.

FIG. 7 depicts the FEC framing state machine. Once the data is aligned, it is checked with the S3062 Reed Solomon (RS) decoder. Reed Solomon a encoding consists of generating parity bytes that are an algebraic function of the user data. There are 2*T parity bytes added to the payload data, where “T” is the number of correctable bytes in the block. The decoder computes 2*T syndromes of the received FEC block, including the FSB, and computes an error locator polynomial as well as a magnitude polynomial from the 2*T syndromes. These latter two polynomials provide the information necessary to detect and correct the erred bytes (up to T bytes per FEC block).

If the decoder detects a correctable error, it does so whether the error is in the FSB, the data or the parity bytes themselves. It also keeps statistics on the number of errors and the error type. There is a count for the number of “1”s corrected, the number of “0”s corrected and the total number of bits and the number of bytes corrected. Since up to 8 errors can be corrected per byte, the number of bytes corrected can be as much as 8 times less than the number of bits corrected.

There is also a count for uncorrectable frames, those that have more than T errors in them. In those frames, the bits and bytes, which are corrected, are still counted and the uncorrectable frame count is incremented. It is not possible to guarantee that the circuit will be able to find all of the uncorrectable frames. If the frame has been corrupted in such a way that it still looks like a valid frame, it will be treated as such. Therefore, if uncorrectable frames are seen, there is a reasonable chance that there were more uncorrectable frames than those which were counted. Furthermore, the corrected bit and byte counts become suspect since some of the bits and bytes “corrected” may have been corrupted instead.

All of the error counts run continuously, regardless of whether the FEC decoder is in or out-of-frame. Software ignores the counts when the decoder is out-of-frame and ignore the first count read when the decoder goes in-frame. The counts accumulate for a period delineated by the 1-second tick. Upon receiving each tick, the count is transferred to a software-readable register and the count is cleared.

The number of bytes corrected is also indicated on the FEC_ERR signal on the FEC_ERR pin (not shown). It is held high for two LKOUTP/N clock periods for each byte corrected. It is held high for the whole of an uncorrectable frame. A whole 1020-byte frame is output in 510 ticks since the S3062 (12) has a 2-byte wide interface (16 bits). The FEC_ERR signal is also held high when the decoder is out-of-frame. Between errors, the FEC_ERR signal is held low for two CLKOUTP/N ticks. Thus, if a FEC uncorrectable frame is followed by a FEC frame with 2 corrected bytes, the signal will be high for 510 ticks, low for 2, high for 2, low for 2, high for 2 and then low until the next error is seen.

The FEC framer can be programmed to ignore certain bits in the 4-byte FSB group when those bits are used for a data link. The data link bits, used for the received data link, are defined by the ‘FEC Out-of-Frame FSB Check Enable/Data Link Bit Selection’ register. If the ‘RX FEC Data Link ON’ register pin (signal) is enabled, the appropriate bits are copied from the FSB group and shifted serially out, LSB first, of the ‘FEC Receive Data Link Out’ pin (RXFECDL) along with a clock (RX_FEC_DLCK). The clock only runs when there is data to be output; it is a gapped clock with a frequency of CLKINP/N divided by 12. Since the S3062 (12) may accept input clocks from 155.52 MHz/16 to 2678.57 MHz/16, the serial clock output can vary from 810 kHz to 13.95 MHz.

In the reverse direction, if the ‘TX FEC Data Link ON’ bit is enabled, a serial clock is provided on the TX_FEC_DLCK pin, which is the TXCLKP/N divided by 12, and data is brought in from the ‘FEC Transmit Data Link’ (TX_FEC_DL) I/O pin. The data is inserted into the 4-byte outgoing FSB group in the locations specified by the ‘FEC Encode FSB/Data Link Bit Selection’ register.

Returning to FIG. 4a, it can be alternately stated that the figure depicts an IC transmission repeater 12 with auxiliary data link. The repeater 12 comprises a decoder 54 having a first input operatively connected to line 50 to receive a first stream of information including a second message written in a second group of selectable overhead bits, described above as the data bits. As noted above, the decoder 54 receives the first stream of information at a plurality of data rates. The decoder 54 reads a first group of selectable overhead bits, defined above as the FSB group, to synchronize the first stream of information into a first frame structure including a block with a data section and a header section.

FIG. 8 depicts an exemplary first frame structure. The first frame structure is shown with a header section and a data section. Returning to FIG. 4a, the decoder 54 has a second input on line 62 to select the first and second group of overhead bits. A first output on line 64 provides the second message recovered from reading the second group of overhead bits.

The decoder's 54 reception of the first stream of information also includes receiving a first message, which is the intended or primary message embedded in the data section of the block structure (see FIG. 8). The decoder 54 reads the data section to recover the first message. The decoder 54 has a second output on line 66 to provide the first message.

Returning to FIG. 8, the decoder's synchronization of the first stream of 1o information into the first frame structure includes the header section having a plurality of m bits and a data section having a plurality of p bytes. FIG. 8 specifically depicts an example where m=1 byte and p is permitted to vary. However, the present invention is not limited to any particular number of bytes in the header section. In some aspects of the invention the data section also includes parity bytes. The decoder reads the first and second group of overhead bits from the header section. The first group of overhead bits in the header section is labeled with a “1” and the second group of overhead bits is labeled with a “2”.

Returning to FIG. 4a, a deinterleaver (deMUX) circuit 52, having an input on line 50, accepts the first stream of information. The deinterleaver 52 has a plurality of n outputs on line 68 to provide the first stream of information deinterleaved into a plurality of n parallel data streams. The nth output is depicted with a dotted line. The decoder 54 has a first input which is a plurality of n inputs on line 68 to accept the plurality of n parallel data streams from the deinterleaver circuit 52. The decoder 54 reads the first group of overhead bits from the n parallel header sections to synchronize the first stream of information. The decoder 54 reads the second group of overhead bits from n parallel header sections to recover the second message output on line 64.

The decoder second input on line 62 accepts commands to select the first group of overhead bits from a plurality of q overhead bits in the range from zero to m bits. As shown in FIG. 8, where m=1 byte, the number of bits in the first group can vary from zero to 8. Likewise, the decoder second input accepts commands to select the second group of overhead bits from a plurality of r overhead bits in the range from zero to m bits. That is, the bits not selected for use by the second group are dedicated for use in the first group of overhead bits. In the figure, 3 bits have been selected for the second group of overhead bits.

Further, the decoder's second input on line 62 accepts commands to select a first location for the second group of overhead bits in the header section. In the figure, the second group of overhead bits are located in bit positions 3, 4, and 5. However, it is understood that the second group of overhead bits can be selected to located in any bit position in the header section.

FIG. 9 illustrates an exemplary interleaved frame structure. The decoder second input on line 62 (see FIG. 4a) accepts commands to select the number of second group overhead bits, in the range from zero to m bits, for each of the header sections of the n parallel data streams. FIG. 9 explicitly shows four (n=4) parallel data streams and a header section of one byte (m=1 byte). The locations for the second group of overhead bits in each of the header sections of the n parallel data stream header sections are also selectable. In the first data stream, four bits are selected for the second group of overhead bits, and they are located in positions 4-7. In the second data stream, six bits are selected for the second group of overhead bits, and they are located in positions 1-6.

Returning to FIG. 4a, an encoder 70 is shown having a first input on line 72 to accept a fourth message. The encoder 70 organizes a second stream of information into the first frame structure (see FIG. 8) including a block with a header section and a data section. The encoder 70 has an output on line 74 to supply the fourth message written in the fourth group of overhead bits of the header section.

The encoder 70 has a second input on line 76 for selecting a third group of overhead bits for synchronization of the second stream of information. The encoder 70 writes the third group of overhead bits into the header section. In some aspects of the invention the encoder 70 accepts a third message on line 78 which it writes into the data section of the first frame structure. The encoder 70 receives the third message on line 78 in a third stream of information having a first communication protocol. The encoder writes the third message in the data section independent of the first protocol.

The encoder's second input on line 76 accepts commands to select a plurality of r fourth group overhead bits in the range from zero to m bits. The selection of the fourth group of overhead bits includes selecting a second location in the header section. In some aspects of the invention the encoder 70 includes a plurality of n outputs on line 74, where the dotted line represents the nth output, to provide a plurality of n parallel data streams organized in the first frame structure including n blocks having header and data sections. The encoder's second input on line 76 accepts commands to select the number of fourth group overhead bits in the range from zero to m bits, in each of the n header sections, and to select a second location for the second group of overhead bytes in each of the n header sections. The process of selecting overhead bits for a transmitted (second) stream of information is essentially the reverse of the process of selecting overhead bits to read in the received (first) stream of information.

An interleaver (MUX) 80 has a plurality of n inputs connected to the plurality of n encoder outputs on line 74. The interleaver 80 interleaves the n parallel data streams to form the second stream of information at the interleaver output on line 82.

In some aspects of the invention the second, or auxiliary message recovered by the decoder 54 on line 64 is passed through to the encoder 70. That is, the fourth message is the same as the second message. This pass-through is represented in the figure by the dotted line connecting lines 64 and 72. When the auxiliary message is passed through, the number of bits in the second group of overhead bits equals the number of bits in the fourth group. However, the location of the bits in the header sections need not be the same.

If data link bits (second and fourth OH group) have been defined in both the decode and encode FSBs, but the data link add has not been enabled, the data in the link will be passed through. For this to work correctly, the data rate entering the link must be the same as the data rate going out. Therefore, both the FEC decode and FEC encode must be enabled with the same number of bits and error correction rate for the data link to be identical in both receive and transmit FSBs. Note that the number of bits in the FSBs must be the same, not the actual locations of the bits. Table 1 shows a summary of how the data link works given that the appropriate FSB bits have been enabled.

TABLE 1 Data Link Enable RX TX FEC FEC Data Data Link Link ON ON Data Link Description 0 0 Pass-through: data link bits in RX FSBs are copied to the bits in the TX FSBs 0 1 Insert Only: data link information is taken from the TX_FEC_DL pin and inserted in the TX FSBs 1 0 Drop and Continue: data from the RX FSBs goes out on RX_FEC_DL and is copied into the TX FSBs 1 1 Drop and Insert: data from the RX FSBs goes out on RX_FEC_DL. Data from TX_FEC_DL is inserted into the TX FSBs

Assuming that m=1 byte and n=4, a user may define anywhere from 0 to 32 of the FSB bits to be used for the data link. The more bits used for the data link, the fewer there will be available for the FSB framer. If all bits are used for the data link, the framing will not work. To determine the data link rate obtained from the chosen data link bits, the following equation may be used:

LINK RATE=(number of bits chosen for the link/(4*255 bytes*8 bits/byte))*data rate in bits/sec.

For example, consider a 1.25 GHz Gigabit Ethernet link encoded with FEC providing 8 bytes/255 bytes error correction capability. FEC encoding increases the data rate as shown in the FEC Algorithm. In this example, the data rate is 1.25 GHz*255/238=1.34 GHz. If 8 bits are stolen from the FSB for the data link, the data link bit rate is 8/(4*255*8)*1.34 Gb/s=1.3 Mb/s.

Alternately stated, the decoder's second input on line 62 accepts commands for selecting a first number of second group overhead bits in a first location in the header section. The first output of the repeater on line 64 is connected to the encoder first input on line 72 to provide the fourth message, so that the second message is passed through as the fourth message. The encoder's second input on line 76 accepts commands to select the first number of fourth group overhead bits in a second location in the header section. That is, the number of bits in the second and fourth groups must be the same, but not the location of these bits in the header section.

Alternately, the fourth message may originate at repeater 12 without a second message being received. Further, the second and fourth messages may be different. In this circumstance the number of bits in the second group of overhead bits does not necessarily equal the number of bits in the fourth group. Also, a second message may be received, but no fourth message need be transmitted.

Likewise, the first message may be passed through and transmitted as the third message. Alternately, the first and third messages are different, the repeater receives the first message without transmitting a third message, or the repeater transmits a third message without receiving a first message. The operation of the auxiliary communications link is independent of the messages communicated in the data sections of the information streams.

FIG. 10 is a schematic block diagram of a system for auxiliary communications. The system 100 comprises a first repeater 12 as described above. First repeater 12 includes an encoder 70 having a first input on line 70 to receive a fourth message, a second input on line 76 for selecting a third group of selectable overhead bits which synchronize a second stream of information into a first frame structure including a block having a header section and a data section. The second input on line 76 also selects a fourth group of overhead bits to communicate the fourth message. The encoder 70 writes the fourth message into the fourth group of overhead bits in the header section as described above. An output on line 82 provides the second stream of information.

A second repeater 102 includes a decoder 104 having a first input on line 82 to receive the first stream of information. The decoder 104 reads the third group of overhead bits to synchronize the second stream of information into a first frame structure including a block with a data section and a header section. The decoder 104 reads the fourth group of overhead bits to recover the fourth message. The decoder 104 has a second input on line 106 for selecting the third and fourth group of overhead bits, and an output on line 108 to provide the fourth message. Although only two repeater are explicitly shown, it is understood that the first repeater 12 may be connected to transmit to any number of repeaters. Likewise the second repeater 102 may be connected to any number of repeaters to receive information.

FIGS. 11a and 11 b are flowcharts illustrating a method for generating an auxiliary communication link. Although the method is presented as a sequence of numbered steps for the purpose of clarity, no order in the process should be inferred from the numbering unless explicitly stated. Step 200 provides a transmission repeater device. Step 202 receives a first stream of information. The reception of the first stream of information includes receiving the information stream at a plurality of data rates. Step 204 creates a first frame structure including a selectable first group of overhead bits and a selectable second group of overhead bits. Step 206 selects a first group of overhead bits to read. Step 208, in response to reading the first group of overhead bits, synchronizes the first stream of information into the first frame structure. Step 210 is a product where a set of overhead bytes are reserved for use in an auxiliary data link.

The reception of the first stream of information in Step 202 includes receiving a second message in the first information stream. Step 207 selects the second group of overhead bits, and Step 209 a, in response to reading the second group of overhead bits, recovers the second message.

In some aspects of the invention the reception of the first stream of information in Step 202 includes receiving a first message in the first information stream. Then, Step 209 b recovers the first message.

The synchronization of the first stream of information into the first frame structure in Step 208 includes sub-steps. Step 208 a organizes the first stream of information into a block with a header section having a plurality of m bits and a data section having a plurality of p bytes. Step 208 b reads the first group of overhead bits from the header section. The recovery of the second message in Step 209 a includes reading the second group of bits in the header section, and the recovery of the first message in Step 209 b includes reading bytes in the data section.

In some aspects of the invention Step 203 deinterleaves the first stream of information into a plurality of n parallel data streams. Then, the synchronization of the first stream of information into the first frame structure in Step 208 includes forming a header and a data section in each of the n parallel data stream, where the first frame structure of n parallel data streams includes forming a combined header section of n×(m/8) bytes.

The selection of the first group of overhead bits in Step 206 includes selecting a plurality of q overhead bits in the range from zero to m bits. The selection of the second group of overhead bits in Step 207 includes selecting a plurality of r bits in the range from zero to m bits, and includes selecting the location of the second group of overhead bits in the m bits of the header section. When the n parallel data streams are formed, the selection of the second group of overhead bits in Step 207 includes selecting the number of second overhead group bits, in the range from zero to m bits, for each of the header sections of the n parallel data streams. Likewise, the selection of the second group of overhead bits in Step 207 includes selecting locations for the second group of overhead bits in each of the header sections of the n parallel data stream.

In some aspects of the invention Step 212 provides a fourth message. Step 214 organizes a second stream of information into the first frame structure including a block with a header section and a data section. Step 216 writes the fourth message in the header section of the second information stream, and Step 218 transmits the second stream of information.

In some aspects of the invention Step 213 provides a third message, and Step 217 writes the third message to the data section of the second information stream.

Step 215 a selects a third group of overhead bits for synchronization of the second stream of information. Step 215 b selects a fourth group of overhead bits to communicate the fourth message. The writing of the fourth message into the header section in Step 216 includes writing the third and fourth group of overhead bits into the header section of the second stream of information.

The selection of the third group of overhead bits in Step 215 a includes selecting a plurality of q overhead bits in the range from zero to m bits, and includes selecting the location of the q overhead bits in the header section. The selection of the fourth group of overhead bits in Step 215 b includes selecting a plurality of r overhead bits in the range from zero to m bits, and includes selecting the location of the r overhead bits in the header section.

In some aspects of the invention the organization of the second stream of information into the first frame structure in Step 214 includes forming a header and a data section in n parallel data streams. Then, Step 214 a interleaves the n parallel data streams into the second stream of information.

In some aspects of the invention the provision of the fourth message in Step 212 includes using the second message, recovered from the first stream of information in Step 209 a, as the fourth message (pass-through). Then, the selection of the second group of overhead bits in Step 207 includes selecting a first number of bits in a first location in the header section, and the selection of the fourth group of overhead bits in Step 215 b includes selecting the first number of bits in a second location in the header section, where the first and second locations are not necessarily the same.

In some aspects of the invention Step 200 provides a first and second repeater. Step 218 then includes transmitting the second information stream from the first repeater. Step 220 receives the second stream of digital information at a second repeater. Step 222 uses the third group of overhead bits to synchronize the second stream of information into the first frame structure, and Step 224 recovers the fourth message.

In some aspects of the invention the provision of the third message in Step 213 includes providing the third message in a third stream of information having a first protocol. The writing of the third message in the data section in Step 217 includes writing the third message independent of the first protocol.

Returning to FIG. 4a, regardless of whether or not the data goes through the decoder 54, it must run through the FIFO 56 to become aligned with the transmit clock. The transmit clock may be identical to the receive clock or it may have a different phase or different frequency. The FIFO 56 is simply a 256×32 bit circular memory with the write address running on the receive clock (divided down CLKINP/N) and the read address running on the transmit clock (divided down TXCLKP/N). When the S3062 is reset the addresses also reset, offset by 180 degrees.

The FIFO is used as follows:

1) If FEC is not enabled, the transmit clock is the same frequency as the receive clock and the FIFO handles the possible phase difference between the two clocks.

2) If data coming into the S3062 is FEC encoded, but the data going out is not, the frequency of the receive clock is higher than the transmit clock because of the extra frame synchronization and parity bytes. Those extra bytes are not sent through the FIFO. The FIFO acts like an elastic store, passing data bytes, but not the FSB or parity bytes. This shows how the frequency difference is handled internally by the FIFO.

3) If data entering into the S3062 is not FEC encoded, but the data going out is, the frequency of the transmit clock is higher than that of the receive. The extra FSB and parity bytes, however, are not added to the data stream until after the FEC encode block. Prior to that block, there are fewer data bytes than clock ticks so that an internal signal is used to stop the data flow when the FSB and parity bytes are being sent out. The FIFO again acts like an elastic store, receiving data bytes with the slower receive clock and only sending them out with the faster transmit clock when not halted. Thus it handles the frequency difference.

4) If data entering into and leaving the S3062 is FEC encoded, the receive side stores data bytes into the FIFO as mentioned in point (2) and the transmit side only takes data out when it is not halted by the internal stop signal, as mentioned in point (3). The FIFO again works as an elastic store.

Since the transmit clock is derived from the receive clock externally to the S3062, the FIFO's read and write addresses will not normally overtake each other. However, if the addresses do come within 2 to 6 addresses of each other, the S3062 will force them back apart and indicate the re-centering with an interrupt At reset, the addresses start 180 degrees apart. If the FEC decoder is OFF, data starts passing through the FIFO immediately. If the decoder is ON, no data goes through until the FEC framer is synchronized and one frame has been decoded.

Note that if the transmit clock has the capability of free running when the receive clock has failed, all but the FEC and differential decoding portions of the chip will continue to function. This will permit a signal (in the case of SONET/SDH, a valid line AIS signal) to be sent out so that downstream devices will not also lose clock.

With respect to the FIFO, if the S3062 is operating with the use of an external PLL (and FEC decode is OFF), the FIFO pointers may have to be re-centered to avoid an unexpected address collision due to clock drift or another unexpected event.

When the transmit clock is generated from the receive clock through an external PLL circuit, it may drift from the receive clock's frequency until the PLL has locked. While the clocks are drifting, the FIFO pointers will move closer to each other. When the PLL circuit has finally locked, the pointer positions relative to each other are unknown and should be pushed 180 degrees apart to prevent unexpected collisions due to clock drift or another unexpected event. If the FEC_ENC pin is enabled, software may force the FIFO to re-center by changing the FEC capability in the ‘FEC Encode General Controls’ register. A valid but incorrect value in these registers will cause the S3062 to remove more, or fewer, bytes than it should within the FIFO, forcing the read and write pointers to collide. The collision will trigger an interrupt indicating that the FIFO has re-centered. Software may then service the interrupt and change the ‘FEC Capability’ bits to their normal values before the pointers move significantly from their initialized positions, 180 degrees apart.

For example, if the FEC capability is set to 8-byte correction, each 255-byte block has 238 bytes of data, 1 FSB byte and 16 redundant bytes. If the capability is set to 7-byte correction, each 255-byte block has 240 bytes of data, 1 FSB byte and 14 redundant bytes. Therefore, if the chip is supposed to be generating 8-byte correction and the user changes it to 7-byte correction, 2 (240−238) extra data bytes will be removed from the FIFO each time a 255-byte block passes through the FIFO. The read pointer will move 2 locations closer to the write pointer per 255-byte block. If the read pointer starts 180 degrees (256 locations) away from the write pointer, they will collide within 128 (256/2) 255-byte blocks. When a collision occurs, the hardware forces the pointers 180 degrees apart again.

If the byte correction is changed by 1, the pointers will move apart 2 locations every 255 bytes (as described in the example above). This is the slowest the pointers will move.

If the byte correction is changed by 8, (i.e. from FEC encode ON, 8 byte correction to FEC encode OFF), the pointers will move apart 17 locations every 255 bytes. 255 bytes of data will be removed from the FIFO every block instead of 238. 255−238=17. This is the fastest the pointers will move. The time required to output 255-bytes is 255*2*TXCLK=510*TXCLK.

Returning to FIG. 4a, after the FIFO 56, the data may be selected by a pass-through MUX 300 to pass data to the encode block 70, which includes both FEC and differential encode functions. Like the FEC decode, the FEC encode function can be turned ON or OFF from a signal pin (FEC_ENC). Once the pin has been tied high, software, if present, can disable the feature through the FEC Encode OFF register bit to permit encoding to be turned OFF and ON during tests. The encoder 70 inserts the FSB at the front of each block of bytes and then generates the parity bytes required for error correction over the FSB and data bytes. Note that both the error correction capabilities of the encoded link and the FSB value sent by the encoder 70 can be different than that expected by a subsequent decoder. By default, however, they are the same.

If the data link bits have been selected in the ‘FEC Encode FSB/Data Link Bit Selection’ register, the encoder brings data into the link from the ‘FEC Transmit Data Link’ (TX_FEC_DL) I/O pin or it is passed through from the received data link. The choice of which data is transmitted is determined from the ‘TX FEC Data Link ON’ register bit but both decode and encode data links must be defined for the data to be passed through. For this to work correctly, the data rate entering the link must be the same as the data rate going out. Therefore, both the FEC decode and FEC encode must be enabled with the same error correction rate and the number of bits defined for the data link must be identical in both receive and transmit FSBs. Note that the number of bits in the FSBs must be the same, not the actual locations of the bits. Table 1, above, shows a summary of how the data link works given that the appropriate FSB bits have been enabled.

Errors are injected into the data, the optional selection includes:

which stream(s) to corrupt out of the 4 interleaved streams;

whether to corrupt the FSB or the data bytes; and

which bits in a byte should be corrupted. If data bytes are to be corrupted, the user may also select the number of bytes in each 255-byte block to be corrupted (up to 15).

Without the FEC turned ON, the notion of streams does not exist, but the data is still arranged inside the chip as a 4-byte wide path. For example, if the user specifies 4-bytes of corruption on stream #4, the least significant byte of the internal data path will be corrupted for the first four words every 255-bytes. At the output of the S3062, after the streams have been interleaved, the errors will show up every 1020-bytes in byte numbers 4, 8, 12 and 16.

After leaving the encoder 70 the data is multiplexed back up to 16 bits and exits the chip. All the SONET/SDH 32 and Gigabit Ethernet 30 monitoring circuits shown in FIG. 4a are powered down if the S3062 is in pass-through mode; thus, less power is consumed than in other modes. The FEC block 70 are also powered down if it is not enabled.

The S3062 algorithm is based upon the (n,k) Reed Solomon Code where n is the block length of the code and k is the number of user symbols per block. The code is defined over the Galois field (2⁸) resulting in symbols of eight bits, i.e. a byte. It belongs to the family of systematic linear cyclic block codes based on the generator polynomial given by:

G(x)=_(i=0)Π^(2T−1)(x−α ^(i))

where T=(error correcting capability of the RS-Code) and

α⁰=01 hex and α¹=02 hex, over the primitive

polynomial P(x)=x8+x4+x3+x2+1 on GF(2⁸)

Where a is a root of the primitive polynomial x₈+x₄+x₃+x₂+1. A data byte (d₇, d₆ . . . d₀) is identified with the element d₇*α⁷+d₆*α⁶+ . . . +d₀ in GF(256), the finite field with 256 elements. The “rate” of the code is defined as the ratio of the total symbols in a block to the user data symbols. Since, in this case, symbols are bytes, the code rate is the total number of bytes in a block divided by the number of the user's data bytes in the block. The S3062 supports six different code rates, all based on the same generator polynomial.

TABLE 2 RS Code Rate Expansion Code Rate Showing Bandwidth Reed- Expansion Example of Increased Input Clock Solomon Error Correcting due to Code Words Frequency for STS-48/STM-16 Code Capability & FSB (MHz) (255,23) 8 bytes per 255-byte 255/238 = 7.14% 155.52*255/238 = 155.52 * 15/14 = block increase 166.63 (255,24) 7 bytes per 255-byte 255/240 = 6.25% 155.52*255/240 = 155.52 * 17/16 = block increase 165.24 (255,24) 6 bytes per 255-byte 255/242 = 5.37% 155.52*255/242 = 163.87 block increase (255,24) 5 bytes per 255-byte 255/244 = 4.51% 155.52*255/244 = 162.53 block increase (255,24) 4 bytes per 255-byte 255/246 = 3.66% 155.52*255/246 = 155.52 * 85/82 = block increase 161.21 (255,24) 3 bytes per 255-byte 255/248 = 2.82% 155.52*255/248 = 159.91 block increase

The S3062 internally divides the data down into four steams (n=4) to reduce the internal clock speed. Each stream has a dedicated RS codec that may correct up to 8 erred bytes. Since the four codecs are running in parallel, a burst of 32 erred bytes may be corrected. Thus, the error correcting capability of the S3062 is four times better than what might be expected by looking at the simple error correction capability of the RS algorithm. In the S3062, the RS(255,239) code provides a burst error correcting capability of 32 bytes (4×8-bytes) or 256 bits.

The default code used by the S3062 is the RS(255,239). This algorithm puts 1 FSB, 238 data bytes and 16 parity bytes into a block. See FIG. 6 for the block format. As shown in Table 2 above, this version of the algorithm can correct up to 8 erred bytes in the 255-byte block. The choice of other code rates allows the user to optimize overall system performance by balancing error-correcting capability against the channel degradation due to rate expansion. The default error correcting code may only be changed by programming the ‘FEC Capability’ register bits.

FIG. 12 is a schematic block diagram illustrating the clocking associated with FEC. When FEC is bypassed or when full FEC (both decoding and encoding) is enabled, the input clock rate to the device is equal to the output clock rate and no external clock circuitry is required. When the S3062 is used for encoding only, or for decoding only, the input clock rate and output clock differ in proportion to the rate expansion factor listed in bold face in Table 3.

TABLE 3 RX/TX Clock Divider Default Values RX TX Clock Clock FEC_DEC FEC_ENC Divider Divider Description 0 0 4 4 Neither encode nor decode: data stream without FEC 0 1 14 15 Encode only: start of system-wide FEC data stream 1 0 15 14 Decode only; end of system-wide FEC data stream 1 1 4 4 Encode Decode: middle of system-wide FEC data stream

Normally the clock dividers should be programmed to be either 255/248, 85/82, 255/244, 255/242, 17/16 or 15/14 to match the error corrections of 3, 4, 5, 6, 7 or 8 respectively. If the clock to the transmit section is different from the one derived from the receive clock, the dividers may be programmed with different values in the range of 1 to 255.

Gigabit Ethernet (GBE)

8B/10B Coding is transmission coding scheme used for the Gigabit Ethernet. Each 8-bit data byte is represented by two distinct 10-bit words. For example:

000 11000→110011 0100 or 001100 1011

512 code words represent 256 bytes, and 12 special function code words also exist. Several 8-bit codes are only mapped to one 10-bit word and not all 10-bit words are complete complements of each other.

TABLE 4a 8B/10B Sample Data Codes Byte Code Word Code Word Bal/ Name Value 8 Bits (RD−) (RD+) Unbal /D24.0 18h 00011000 110011 0100 001100 1011 Balanced /D24.0 19h 00011001 011001 1011 100110 0100 Unbalanced /D26.0 1Ah 00011010 101001 1011 010110 0100 Unbalanced /D27.0 1Bh 00011011 110110 0100 001001 1011 Balanced /D28.0 1Ch 00011100 110001 1011 001110 0100 Unbalanced /D29.0 1Dh 00011101 101110 0100 010001 1011 Balanced /D30.0 1Eh 00011110 011110 0100 100001 1011 Balanced /D31.0 1Fh 00011111 101011 0100 010100 1011 Balanced

The Purpose of 8B/10B Coding is to maintain DC balance, ensuring that a data stream can be AC coupled without distortion, and to avoid short-term DC offsets by minimizing run length. Invalid code words and code word sequences that break parity rules are possible error types. There are three basic rules that are used in transmitting 8B/10B data:

A data word NEVER contains more than 4 consecutive ones or zeros, this reduces the “Run Length” on the line;

A word containing 4 zeros may only be followed by a word with 5 or 6 zeros; and

A word containing 6 zeros may only be followed by a word with 5 or 4 zeros. Minimizing the “Run Length” avoids any short term DC offsets.

Parity tracks the number of ones and zeros on a line in an attempt to keep their numbers equal +/−1 bit. The “Ideal” pattern is “1 0 1 0”. For example:

101010101010101010101010101010101010 Number of 1s = Number of 0s

An equal number of ones and zeros over an entire line ensures the data stream may be AC-coupled onto a medium without distortion.

A balanced code word has an equal number of ones and zeros. For example:

/D24.0 0011001011 5 zeros and 5 ones

inverse 1100110100 still has 5 zeros and 5 ones.

An unbalanced code word has an unequal number of ones and zeros. For example:

/D25.0 1001100100 6 zeros and 4 ones

inverse 0110011011 4 zeros and 6 ones.

The choice of which code word to use depends on the running disparity. Single-bit indications of which way the ± bit parity imbalance is leaning, are updated on a code-word by code-word basis.

Positive Running Disparity (RD+)→More 1s than 0s being transmitted

Negative Running Disparity (RD−)→More 0s than 1s being transmitted.

Running disparity is used in 8B/10B encoding to determine which of the two possible 10-bit codes to send for each 8-bit word. Running Disparity is calculated on the basis of sub-blocks—a six-bit, and then a four-bit, sub-blocks that make up the complete 10 bit word. Running Disparity is “+” if the sub-block contains more ones than zeros or if the six-bit sub-block is 000111, or the four bit sub-block is 0011. Running Disparity is “−” if the sub-block contains more zeros than ones or if the six-bit sub-block is 111000, or the four-bit sub-block is 1100. If the Positive and Negative sub-block criteria has not been met, the running disparity will remain unchanged at the end of the sub-block.

Sequence of 8-bit words to be sent:

00111111 11110111 11111100 D31.1 23.7 D28.7

The encoder begins with RD− and selects appropriate 10-bit code word for D31.0:

Select from RD− column.

Then, the encoder examines previously sent word to determine code word for D23.7:

Examine “101011 1001”→Select from RD+ column.

Then, the encoder examines previous sent word to determine code word for D28.7:

Examine “000101 1110”→Select from same (RD+) column.

Transmitted sequence:

^(RD−) 101011 1001 ^(RD+) 000101 1110 ^(RD+) 001110 0001 ^(RD+)

The following is an example of f 8B/10B Coding Example Using RD. 8 bit data sequence:

00111111 11110111 11111100

Unequal number of 1s and 0s (19 Ones, 5 Zeros)

Long runs of 1s and 0s possible

Transmitted 10-bit encoded sequence:

^(RD−) 101011 1001 ^(RD+) 000101 1110 ^(RD+) 001110 0001 ^(RD+)

Balanced Line (15 Ones, 15 Zeros)

Maximum run length of 4 consecutive 1s or 0s.

With respect to word alignment, Data is searched for a 10-bit “special” K28.5 word or a Comma. The choice of which K28.5 (or Comma) to search for is dependent upon the current running disparity (RD).

K28.5 word 110000 0101 or 001111 1010

Comma (1st 7 bits of K28.5) 1100000 or 0011111.

Once the first K28.5 word is found, the data going into the Monitor Block is aligned on that word. Aligned words are sent to Monitor Block in sets of 3 or 4. If four words are sent, a “fourth word enable” is sent to the Monitor Block. Error monitors run continuously, regardless of alignment.

Referring again to Fig.. 4 a, in the GBE mode the data flows through the chip 12 as if it were in pass-through mode, but it is also routed to the Gigabit Ethernet monitor 30 from the 32-bit internal bus.

FIG. 13 is a schematic block diagram illustrating details of he GBE monitor 30. To find the 10-bit Gigabit Ethernet words, the alignment block 400 searches the 32-bit data either for the 10-bit K28.5 word (which is actually one of two words, depending on the running disparity) or for a comma. The K28.5 alignment value is the default for the S3062 but may be changed to a comma by enabling the IEEE synchronization method, with the ‘IEEE ON’ register bit. The error monitors run continuously (except when reset is asserted) and are not dependent on the alignment block 400. Note that the data entering the GBE block is in 32-bit words, while GBE data is aligned on 10-bit boundaries. To handle this difference, the alignment block 400 either outputs three or four 10-bit words on line 402, using an enable signal on line 404 to notify the downstream blocks that the fourth 10-bit word is present.

The error monitor 406 checks for synchronization. It is a circuit searching for another K28.5 byte. If one is found with a different alignment, the circuit 406 pulses the SYNC_LOSS signal on line 408 for 2 CLKOUTP/N periods, sets the sync loss interrupt bit and signals the alignment block 400 on line 410 to change to the new alignment. This circuit 406 may be changed to the standardized, IEEE 802.3z state machine if the ‘IEEE ON’ register bit is set. The IEEE algorithm generates a SYNC_LOSS error indication that is a level signal as opposed to the pulsed signal described above. SYNC_LOSS will be active while synchronization is lost and will be inactive once the state machine synchronizes. When synchronization is lost, the alignment block 400 searches for comma characters with new alignments.

The error monitor 406 checks the 10-bit words for invalid codes. It indicates that the received character is not a valid codeword considering the current running disparity. Even if the codeword appears in the Valid Code Group Table 36-1&2 in IEEE 802.3 z, the current running disparity might disqualify the codeword from being valid. If the codeword does not appear in the IEEE 802.3 z table, the codeword is not valid. When an invalid code is found, the INV_CODE I/O pin on line 412 pulses for two CLKOUTP/N periods.

FIG. 14 is a logic diagram depicting the determination of a running disparity (RD) error. Only errors in the data stream (i.e. invalid code words) can cause characters composed of more than 6 ones or 6 zeros. The received codeword is used to calculate the new value of running disparity, regardless of the character's validity. If the received codeword is found in a different column of the 802.3 z Valid Data Character table than expected, a RD error will be discovered and an INV_CODE will be declared. This determination is made independent of the parity calculation.

The RD calculation is only used for codeword validation. A separate RD error count/flag is not available to the user. The user may, however, correlate the parity error count to the invalid code count to determine the cause of the failure.

FIG. 14 depicts the methodology used to determine which running disparity column (RD− or RD+) of the IEEE 802.3z Valid Data Character table to find the next received/sent 8B/10B code word. The last four bits (f g h j) of the previous received/sent codeword are examined first. If the codeword is determined to have more ones or zeros, the desired RD column is determined and the examination of that character may stop. If the bits are balanced (has the same number of ones and zeros) and are NOT a special case (1100 or 0011), the first six bits (a b c d e i) of that code-word must also be examined to determine the RD column location of the next codeword. If the examined six bits turn out to be balanced and are NOT a special case (000111 or 111000), the next codeword will come from the same running disparity column as the examined codeword.

An additional check is performed on the receive codeword which relates to the running disparity properties of the 8B/10B code. Any two occurrences of 10 bit characters composed of 4 logic ones (i.e. 010010 1001), without the occurrence of a character composed of 6 ones (i.e. 111010 0101) in between, is flagged as a parity error. Any number of characters with equal numbers of ones and zeros are allowed between the two characters composed of 4 ones, with no parity error. The same method applies to the alternate case where a character composed of 4 ones is required to separate any two characters composed of 6 ones, each. This mechanism ensures that both the ones and zeros density of the serial data stream are never more than a single bit from 50%, at the boundaries of any two characters. Parity error checking provides simple testing of dc balance but does not perform a full IEEE 802.3 z Table 36-1&2 lookup based on an IEEE compliant RD calculation. The parity error checking provides a means of verification of non-IEEE compliant codes, which achieve DC-balance in a similar fashion. The parity error indicator is labeled as DISP_ERR on line 414.

The error status points (SYNC_LOSS, INV_CODE, and DISP_ERR) are output on individual I/O pins, on lines 408, 412, and 414, respectively. Additionally, each one of these points generates a maskable interrupt to the processor. In the case of an INV_CODE, DISP_ERR, and a SYNC_LOSS created by the single K28.5 algorithm, an interrupt is generated each time one of the signals pulses. When SYNC_LOSS is created by the IEEE algorithm, an interrupt is generated on both transitions into and out of the synchronization state. The monitors for invalid codes and parity errors each check up to four words during each clock cycle, but only output one error per clock cycle. Thus, when INV_CODE is active, it represents up to 4 invalid codes. Similarly, when DISP_ERR is active, it represents up to 4 parity errors.

Activity counts for each of these status points are accumulated, individually, in error count register 416. SYNC_LOSS activity is only counted when it transitions from in-sync to loss-of-sync for the IEEE mode and counts the number of new alignments found for the default mode. A count of the combined invalid codes and parity errors are also generated. The activity counts are 100% accurate, unlike the error signals on the INV_CODE and DISP_ERR I/O pins.

A performance monitoring tick on line 418 is used to transfer accumulating counts from the count registers 416 on line 420 into static holding registers (not shown) that can be read via the processor interface. All count registers are set to zero at the start of a given count cycle. The tick, which typically occurs every second, can come from a clock connected to the PM_CLK I/O pin or, in the case where a clock is not available, from a software write.

Table 4 describes the effect of certain types of corrupted characters on the invalid codeword and parity error counts. It is intended to be an aid in correlating the corruption type to the error count.

TABLE 4b Invalid Codeword/Parity Error Correlation Invalid Codeword Parity Error Corruption Type Count Count Received character appears in IEEE 802.3z table 36-1 or 36-2 No Change No Change and is the correct disparity for the current RD (i.e it appears in the correct disparity column of the IEEE 802.3z tables). The parity of the character is either neutral or NOT neutral. Received character appears in IEEE 802.3z table 36-1 or 36-2 Add No Change but does NOT match the currect RD (i.e. the character appears in the wrong disparity column of the IEEE tables). The parity of the character is neutral (i.e. the character is composed of an equal number of ones and zeros). Received character appears in IEEE 802.3z table 36-1 or 36-2 Add Add but does NOT match the current RD. The parity of the character is NOT neutral (i.e. the character does not contain an equal number of ones and zeros). Received character does NOT appear in IEEE 802.3z table Add No Change 36-1 or 36-2. The parity of the character is neutral. Received character does NOT appear in IEEE 802.3z table Add Parity OK: No Change 36-1 or 36-2. Parity Error: Add The parity of the character is NOT neutral.

SONET/SDH

Returning briefly to FIG. 4a, in SONET/SDH mode, the data enters the device through the de-multiplexer 52 or the differential/FEC decoder 54 and enters the FIFO 56 as described in the pass-through section. The data then continues on to the transport overhead monitoring block 32 that is described below.

FIGS. 15 and 16 depict exemplary SONET frame structures, including the locations of the transport overhead bytes within the SONET/SDH frame. After the receive data has run through the FIFO, the LOS block of SONET monitor monitors it for all zeros. When 26.337 μs have passed with only zeros being detected, a loss of signal (LOS) is declared (active high) and sent to both an I/O pin and an interrupt bit in a software register. LOS is de-activated following the detection of two valid, consecutive frame alignment patterns without a LOS re-occurring. A performance monitoring tick is used to transfer to the PM register a single-bit indication of whether or not LOS has occurred since the last tick. This register is provided to simplify the gathering of performance monitoring statistics according to the SONET/SDH standards.

The performance monitoring tick, which typically occurs every second, can come from a clock connected to the PM_CLK I/O pin or, in the case where a clock is not available, from a software write.

The Frame and Byte Alignment block examines the data stream coming from the FIFO for 3 A1s and 3 A2s, which determine both the byte and the frame boundaries. Having found the boundaries, the block then sends a frame pulse to the Frame Counter and arranges the data stream so that it is byte aligned for the following blocks. Then the block stops monitoring the data until the Frame Check block indicates that it is Out-of-Frame (OOF) and a search for a new alignment and frame must be started. Note that while this block is searching, the data continues to pass with the previous alignment. Data is unaffected until this block sets the new boundaries.

The Frame Check block determines whether the receiver is in-frame or out-of-frame. In-frame is defined as the state where the frame boundaries are known. Out-of-Frame (OOF) is defined as the state where the frame boundaries of the incoming signal are unknown. OOF is declared when a minimum of four consecutive erred framing patterns have been received. The maximum OOF detection time is 625 μs for a random signal. The SONET specification requires that the framing algorithm used to check the alignment is designed such that a 1×10⁻³ BER does not cause an OOF more than once every 6 minutes. The S3062 algorithm examines the last A1 byte and the first four bits of the first A2 byte for a total of 12-bits to guarantee this requirement.

When in an OOF condition, this block moves back to the in-frame condition upon detecting two successive error-free framing patterns. This implementation of the frame check circuit clears OOF within the required 250 ms interval. Failure to obtain a frame within 3 ms (OOF persists for 3 ms) results in a Loss-of-Frame (LOF). Both OOF and LOF signals are connected to I/O pins and register bits to keep the user informed of the S3062's state. Similarly to LOS, the performance monitoring tick transfers to the ‘PM register’ a single-bit indication of whether or not OOF occurred since the last tick. NOTE: OOF is also referred to as Severely Erred Frame (SEF) in the SONET standards.

FIG. 17 is a logic diagram illustrating the operation of the LOS/OOF state machine. The LOF error indication is implemented by using a 3 ms integration timer to deal with intermittent OOFs when monitoring for LOF. The 3 ms integration timer consists of an OOF timer and an in-frame timer that operates as follows:

The in-frame timer is activated (accumulates) when in-frame is present. It stops accumulating and is reset to zero when OOF is present; and The OOF timer is activated (accumulates) when OOF is present. It stops accumulating when the signal goes in-frame. It is reset to zero when the signal remains in-frame continuously for 3 ms (i.e., the in-frame timer reaches 3 ms).

The LOF state will be entered if the accumulated OOF timer reaches the 3 ms threshold. The LOF state will be exited when the in-frame timer reaches 3 ms. The following figure depicts the LOF and OOF (SEF) state machine that is implemented.

The frame pulse from the Frame and Byte Alignment block resets the counter within this block to the frame boundary. The counter operates at STS-3/STM-1, STS-12/STM-4, or STS-48/STM-16, depending on RATESEL[1:0] inputs. It counts bytes (9 rows×90 columns×N STS-1s) to find the location of all overhead bytes and generate the timing signals and enables required by all of the other blocks. As an example, it generates a signal which controls when the scrambler block scramble, or does not scramble the bytes. It also generates an enable for the insertion of the B1 byte at the correct time and another for the insertion of the B2 byte.

The Section Trace block receives a signal from the Frame Counter block indicating the location of the J0 byte. This block checks the J0 byte for a repeating message which is either 1, 16 or 64 bytes long, as defined by the ‘Length’ register bits. A programmable register also defines the required number of repetitions (either 3 or 5) that must be seen before the J0 message is considered valid. Messages are compared against a message specified by the expected section trace memory and mismatches are flagged. Inconsistent errors are also flagged when no repeating messages are seen. Similarly to LOS, the performance monitoring tick transfers to the ‘PM Register’ a single-bit indication of whether or not a mismatch and/or an inconsistent error occurred since the last tick.

The block can, if requested, search for a message start and put it in the first location in memory. By default, 16-byte messages are expected to have a 1 in the most significant bit of the first byte of the message and 0s in that bit position for the other 15 bytes. Therefore, if a message is 16 bytes long, the byte to go in the to first memory location will contain a value of 1 in the MSB. This is compliant with SDH Section Trace Messaging as stated in G.707. By default, 64-byte messages are expected to be ASCII strings terminated by a carriage return and a line feed (0×0d and 0×0a). Therefore, if the message is 64 bytes long, the byte to go in the first location in memory will be the one following the line feed. This is compliant with SONET Path Trace Messaging as stated in GR-253-CORE. The defaults may be overridden for both message lengths by setting the 16-byte message to SONET format instead of SDH, and vice versa for the 64-byte message.

If the start of the message is unknown, or the defined message start is neither of the two possibilities described above, hardware may store the messages using the Section Trace memory as a circular buffer. The circular buffer may be enabled by setting the ‘Circular Buffer’ bit in the ‘Section Trace Control: Receive and Transmit’ register. The message length may also be set to 1, 16 or 64 bytes by setting the ‘Length’ bits.

The algorithm used to detect problems in the trace message must be robust to bit errors. This block's algorithm defines valid messages, mismatches and inconsistent errors in accordance with Table 5.

TABLE 5 Section Trace Definitions EXPECTED The value stored in the ‘Expected Section Trace MESSAGE Message’ register. This is user programmable. MATCHED A MATCHED MESSAGE is an incoming message MESSAGE that is identical to the EXPECTED MESSAGE. MISMATCH A MISMATCHED MESSAGE is an incoming MESSAGE message that differs from the EXPECTED MESSAGE. VALID A VALID MISMATCHED MESSAGE is an incoming MISMATCH MISMATCHED MESSAGE that differs from the MESSAGE expected message but has been received 3 (default) or 5 consecutive times. The number of received, consecutive values is programmable with the ‘Check 5’ register bit. The times required to receive a VALID MISMATCHED MESSAGE of length 1, 16, 64 in a system with a BER of 0 or 1 × 10⁻³ are shown in Table 10. VALID A VALID MATCHED MESSAGE is an incoming MATCHED MATCHED MESSAGE that has been received 3 MESSAGE (default) or 5 times, without a VALID MISMATCHED MESSAGE received in between. The number or received, consecutive values is programmable with the ‘Check 5’ register bit. The times required to receive a VALID MATCHED MESSAGE of length, 1, 16, or 64 in a system with a BER of 0 or 1 × 10⁻³ are shown in Table 8. Permitting validation of expected messages to occur without requiring the messages to arrive consecutively shortens the validation time when the bit error rate is high. See Table 8 and Table 10. INCONSISTENT An inconsistent error is declared if neither a VALID ERROR MISMATCHED MESSAGE nor a single MATCHED MESSAGE have been seen in 4 times the time which would normally be required to detect 3 or 5 MATCHED MESSAGES in the presence of BER of 1 × 10^(−3.) Reception of a VALID (MATCHED OR MISMATCHED) MESSAGE clears the inconsistent error. Table 9 shows the length of time hardware spends in searching for a valid mismatch or a single expected message before declaring an inconsistant error. Note that the values of Table 9 are 4 times the worst-case values in Table 8.

TABLE 6 Time Required to Recieve a VALID MATCHED MESSAGE 1-byte 16-byte 64-byte BER Message Message Message BER = 0, detect = 3 375 μs  6 ms  24 ms BER = 0, detect = 5 625 μs 10 ms  40 ms BER = 1 × 10⁻³, detect = 3 750 μs 22 ms 192 ms BER = 1 × 10⁻³, detect = 5  1 ms 28 ms 224 ms

TABLE 7 Time Required to Detect an INCONSISTENT ERROR 1-byte 16-byte 64-byte BER Message Message Message BER = 1 × 10⁻³, detect = 3 3 ms  88 ms 768 ms BER = 1 × 10⁻³, detect = 5 4 ms 112 ms 896 ms

It is unlikely that a false INCONSISTENT ERROR will be raised if the expected message is being sent. Note, however, that when the bit error rate is high, and an incorrect message is being sent, it is more likely that an INCONSISTENT ERROR will be raised than a MISMATCH, especially in the case of a 64-byte message. The reason being is that the probability of receiving three consecutive sets of 64-bytes with no errors is small when in the presence of a BER of 1×10⁻³. To increase the probability of receiving a VALID MISMATCHED MESSAGE, one must increase the amount of time one is willing to wait. For a probability>99.9999%, one must wait the times shown in Table 8 below. Table 8 to Table 7 may be consulted to verify that the probability of receiving an INCONSISTENT ERROR is greater than a MISMATCH in the presence of a high bit error rate.

TABLE 8 Time Required to Detect a VALID MISMATCHED MESSAGE 1-byte 16-byte 64-byte BER Message Message Message BER = 0, detect = 3 375 μs  6 ms 24 ms BER = 0, detect = 5 625 μs  10 ms 40 ms BER = 1 × 10⁻³, detect = 3 2.2 ms 120 ms 2.4 s BER = 1 × 10⁻³, detect = 5 2.6 ms 280 ms 24 s

Note that the times during the BER of 1×10⁻³ are approximate. There is a small probability (1×10⁻¹⁰) that the messages still will not be received, in the times shown.

EXAMPLES

1. BER=0, expected 16-byte message=‘A’, the expected message is being received, no section trace errors are showing and the message detect time has been set to 3. The S3062 sees:

. . . AAAAAAAAAAAAAAA . . .

2. The network connections upstream of this node are changed and this device starts seeing 16-byte message ‘B’:

. . . AAAABBB

After the third B, it declares a mismatch and interrupts software which then reads ‘B’ in the receive section trace memory. The time taken to discover the mismatch after the connection was switched is, in this example, 6 ms: 3 messages*16 bytes/message*1 frame/msgbyte*125 μs/frame.

3. Software informs the network of the problem and the connections are fixed, but now there is a BER of 1×10 ⁻³ on the line. The S3062 sees large numbers of random garbage messages (‘g’) because of all the bit errors:

. . . BBBBggAggggAgA

After the third expected message, the S3062 clears the mismatch and interrupts the software to tell it of the change. The software can then read ‘A’ in the receive section trace memory. The time taken to clear the mismatch after the connection fix is, in this example, 10 messages*16 bytes/message*1 frame/msgbyte*125 ps/frame=20 ms.

4. Now the connections get disturbed again and message ‘B’ is once more being sent, but the line still has a BER of 1×10⁻³ on it.

. . . ggAgBggBgBBgBgBggBgggBgggBBggBBgBgggBBggBgBBggB

The S3062 needs to see 3 ‘B’s in a row to be able to say with certainty that it is getting a valid, mismatched message, not just a bunch of noise. In this example, it does not get 3 ‘B’s in a row before hitting the inconsistent error's timeout value of 88 ms. Therefore, an inconsistent error is declared. Note that there is no reason to read the receive section trace message memory. With the bytes changing inconsistently, there is no message to store, so that whatever the last valid message was (in this example, ‘A’) will still be there.

An ‘As-is’ option allows the received J0 message to be written into the receive section trace memory without validation. If the circular buffer is not enabled the message start search may be used. When a new message start is seen, the old message will be written into the received memory and a new message collection started. If no message start is seen, then the message will be written to memory when the correct length (1, 16 or 64) has been received. This will permit messages, which are less than 16 or less than 64 bytes long, to be lined up correctly in the receive memory.

If the circular buffer is enabled in ‘As-is’ mode, the messages will be transferred to the receive memory after the specified bytes (1, 16 or 64) have been received. In this case, if a 64-byte message is selected, memory need be read only once every 8 ms (64*125 μs) to see new values. To create an 8 ms timer synchronized to the S3062, connect FPOUTB to an interrupt and count 64 frames.

All the bytes in the SONET/SDH data stream, with the exception of A1, A2 and J0/Z0, are normally scrambled and must be descrambled before further overhead processing can be completed. The descrambler and scrambler algorithms are identical, using a generator polynomial of 1+x⁶+x⁷ with a sequence length of 127. The algorithm is frame synchronous, being reset to “1111111” on the most significant bit of the first byte following the last byte of the first row (last Z0 byte) of the STS-N/STM-M section overhead. This bit and all subsequent bits to be scrambled are added modulo 2 to the output from the X₇ position of the scrambler.

The Section BIP-8 block receives data from both the scrambled and descrambled data streams. Bit interleaved parity (BIP) is calculated on the scrambled data. Bit interleaved parity-8 (BIP-8) is a method of error monitoring. SDH standard G-707 specifies it as follows:

“Even parity is generated by setting the BIP-8 bits so that there is an even number of 1s in each monitored partition of the signal. A monitored partition comprises all bits that are in the same bit position within the 8-bit sequences in the covered portion of the signal. The covered portion includes the BIP-8”.

The result is then compared with the descrambled B1 byte. Mismatched bits are defined as errors and are shown at the B1ERR output pin and counted internally. If block error counting has been selected, 1 error is counted and shown at the B1ERR output pin and for each erred B1 byte. If block error counting is not selected, 1 error is counted and shown at the B1ERR output pin for each bit that is mismatched (up to 8 errors possible per byte).

A performance monitoring tick is used to transfer the accumulating error count into a static holding register that can be read from the processor and FPGA interfaces. The accumulation counter is then reset to zero. The tick, which typically occurs every second, can come from a clock connected to the PM_CLK I/O pin or, in the case where a clock is not available, from a software write to the ‘PM Tick’ bit.

The tick also transfers, to the ‘PM Register’ a single-bit indication of whether or not a B1 error has occurred within the last second. Thus software can read or not read the count registers based on whether or not the bit is set. Since all of the SONET/SDH counts have an indicator bit in the ‘PM Register’, one read of the ‘PM Register’ would let software know the necessity of further reads.

After the B1 byte has been checked, the data passes on to the line AIS Multiplexer #1. If the user has not requested that line AIS be automatically inserted then the data will go straight through the Line AIS Multiplexer #1. If LOS or LOF has been detected and automatic AIS insertion has been selected, all but the section overhead bytes will be replaced with is. The SONET/SDH specifications require the insertion of AIS upon the receipt of LOS or LOF to prevent downstream blocks from monitoring bad data. A user-requested AIS has no effect on this multiplexer; it only affects the downstream Line AIS Multiplexer #2. This is so that the user may request a downstream line AIS and still monitor the line overhead. Given that the Line AIS Multiplexer #1 has not turned all the line overhead bytes into FFh, the Line BIP-8 block can check the B2 bytes. The B2 byte is allocated in each STS-1 frame for a line error monitoring function. In an STS-N there are therefore N B2s, each one the result of a BIP-8 calculation over a single STS-1 excluding its section overhead. To check that the incoming B2s have been generated correctly, the BIP-8 values are recalculated over the line overhead and the SPE bytes for each STS-1 in each frame after descrambling. The results are then compared to the incoming B2s after descrambling.

If the user has selected block error counting, 1 error is counted for each erred B2 byte. If block error counting is NOT selected, 1 error is counted for each bit that is incorrect (up to 8 errors possible per B2 byte).

A performance monitoring tick is used to transfer the accumulating error count into a static holding register that can be read from the processor and FPGA interfaces. The counter is then reset to zero. The tick, which typically occurs every second, can come from a clock connected to the PM_CLK I/O pin or, in the case where a clock is not available, from a software write to the ‘PM Tick’ bit. To enable the tick to come from software, the user must enable the ‘PM Tick ON’ register bit and activate the Micro Present byte. Then, the user must generate the tick by, every second, writing to the ‘PM Tick’ bit.

The tick also transfers, to the ‘PM Register’, a single-bit indication of whether or not a B2 has error occurred within the last second. Thus software can read or not read the count registers based on whether or not the bit is set. Since all of the SONET/SDH counts have an indicator bit in the ‘PM Register’, one read of the ‘PM Register’ would let software know the necessity of further reads.

The Bit Error Rate block accumulates all B2 bit errors and asserts Signal Fail (SF) or Signal Degrade (SD) to the processor and FPGA interfaces if the number of errors cross pre-set thresholds after pre-set times. The Threshold and Accumulation Period values are software programmable. The threshold and time values default to 1×10⁻³ for signal fail and 1×10⁻⁵ for signal degrade so that this circuit can still be useful if a processor is not connected.

Software must also implement the SONET/SDH fault clearing, after receiving an indication of SF or SD by:

setting the Threshold and Accumulation Period registers to one tenth of the existing BER value;

polling the SD and SF interrupts to see when that one tenth BER indication clears. After the fault has cleared, software can then set the SF or SD Threshold and Accumulation Period registers back to their normal values.

The automatic protection switching (APS) block monitors the least significant 3 bits of the K2 line overhead byte for the Line Alarm Indication Signal (AIS_L: 111) and the Line Remote Defect Indication (RDI_L: 110). If a specified number of consecutive AIS_L values are seen, AIS_L is asserted in a status register, which is accessible by the processor and FPGA. The AIS_L indication is removed when the same number of consecutive non-AIS_L values are seen. RDI_L is handled the same way. The number of consecutive values can be either 3 (for the SDH standard) or 5 (for the SONET standard). This number of consecutive values is configurable via a processor interface control register (default value is 5). Changes of state in AIS_L and RDI_L (to/from AIS_L/RDI_L present/not present to not present/present) indications generate interrupts. Similarly, the performance monitoring tick transfers to the ‘PM Register’ a single-bit indication of whether or not AIS_L and/or RDI_L occurred since the last tick.

The block also monitors K1 and K2 for new values. If a new value of K1 or K2 is seen for 3 consecutive frames, it is latched for software to read and an interrupt is raised. If no consistent K1 value is seen for 12 frames, an “inconsistent K1” alarm is flagged to software. K1 and K2 are used for protection switching.

The synchronization block monitors the S1 line overhead byte for 8 consecutive identical values in the least significant 4 bits. If the nibble differs from the previously acquired Si, the new value replaces the old in a register accessible through the processor and FPGA interfaces. If the new nibble is different from an expected value written in by software, a mismatch is flagged. If the new nibble is the same as the expected value the mismatch is cleared. If 32 frames go by without 8 consecutive identical values, an inconsistent value indication is flagged. To decide that the synchronization source has truly failed, as defined by the standards, software must start a 10 s counter as soon as it receives the inconsistent value indication. If no valid message is detected before the counter runs out, the software must consider that the synchronization reference failed.

The standards specify a 10-second invalid S1 value, not the 32-frame inconsistent value indicator. The 32-frame inconsistent value indicator was designed to assist software and to create a function similar to the K1/K2 standard. The S1 byte is considered valid after 8 consecutive frames and inconsistent after 4 times this interval, or 32 frames.

The S1 value and its error indications are only of use if there are 2 synchronization sources to choose from. If the S3062 device is being used in a repeater, there will only be one clock source available, and no action will be taken if the synchronization reference fails. The user will simply ignore all the Si information.

The STS-N/STM-M M1 byte contains the addition of all the B2 errors that were detected at the far-end. This count is called the Remote Error Indication (REI). The way REI works is as follows:

System X is connected to System Y. Data flows from X to Y and also from Y to X. There is a problem with X's transmitter causing intermittent bit errors. Y sees these errors when it checks B2. It counts them up and sends the count back to X in the M1 byte. X looks at the M1 byte, sees the errors and checks its transmitter. It finds the fault and repairs it.

Since REI reports what the far-end is seeing, it is only useful if the S3062 chip resides in a system where traffic is bi-directional. In a unidirectional system, this data may be kept for performance monitoring statistics.

For statistics, the block adds up the REI values until the performance monitoring tick is received. Just like the B1 and B2 counts, the tick transfers the count to a register accessible by the processor or the FPGA and clears the counter. If no tick is received, the counter stops counting when it reaches a maximum value of 1FE000h errors which is the maximum number of errors that could be received on a STS-48/STM-16 link in a 1.024 seconds. The tick also transfers, to the ‘PM Register’, a single-bit indication of whether or not a REI error occurred within the last second.

The capability of transmitting a user defined value for the M1 byte using overhead insertion via the TX_OH memory is supported if the user wishes to supply the B2 error count arriving in the other direction.

The serializer block serializes onto pins the section and line orderwire (E1 and E2) and the section and line data communication channels (D1-3 and D4-12). The block also generates a gapped 9.72 MHz clocks for the output serial streams. The 9.72 MHz frequency increases by the FEC encode bandwidth expansion factor if FEC encode is ON. The orderwire also requires a frame pulse from this block to mark the most significant bit of the byte. Since the DCCs are bit, not byte oriented, no frame pulses or byte markers are required.

The orderwire must go to an external circuit designed especially for it, but the DCCs may be connected directly to serial HDLC processors such as the MPC860. If the protocol on the DCCs is not standard HDLC, the MPC860 SCC ports may still be used; program them in transparent mode. If the protocol is byte-oriented, the orderwire frame pulses may be used to indicate the first DCC's most significant bit. In this case, however, an external circuit will likely be needed because the orderwire frame pulse is not lined up directly with the DCCs' most significant bits.

Twenty user accessible pins are used by this block and the parallelizer (2 orderwire clocks, 2 orderwire frame pulses, 2 section DCC clocks, 2 line DCC clocks, 4 data out, 4 data in and 4 enable data in). They are also shared by the FPGA port. A FPGA may be connected to extract and insert all the overhead bytes, or, individual devices may be connected to the serial orderwire and DCC ports.

If the FPGA port is not selected, all the DCC signals generated by this block will continue to run, even when the chip is in LOS or LOF. If the data is extracted during a LOS or LOF condition, the data will be garbage. Upon re-acquisition of byte alignment following a LOS or LOF, the location of the frame relative to the previous alignment may have changed. This may lead to extra/fewer bits and serializer clocks in a frame, but the clock period will not be affected.

All received section and line overhead bytes are captured frame-by-frame in the Receive Overhead Memory (X_OH). The memory is divided into 2 pages, X and Y. During the first frame, the overhead bytes are written into page X while the processor and/or the FPGA interface read out of page Y. At the beginning of the next frame, the two pages are swapped and bytes are written into page Y while page X can be read by the processor and/or FPGA. At the beginning of the next frame the pages are swapped again.

The two pages are transparent to the user. If the overhead data is going out the FPGA interface, it looks like a steady stream of overhead data. If software is reading the transport overhead from memory via the processor interface, it always uses the same address to access a particular overhead byte; the address does not change with the page swap. The 2 pages cause a full frame delay between the time the overhead arrives on the chip and the time that it can be read out of the RX_OH memory.

The Overhead Extract State Machine block controls all of the accesses to the Receive Overhead Memory (RX_OH). Write addresses are generated as required to one of the RX_OH pages (page X, for example) while the entire frame of section, and line overhead bytes are written in from the receive data stream. If the to FPGA interface is selected (FPGASEL), then at the same time as page X is being written, the state machine generates read addresses for page Y. 32 bits are read at a time, then held and output to the 8-bit, FPGA interface. AU 1296 overhead bytes (N×27) for an STS-48/STM-16 signal are sent out, in order from the first A1 to the last byte in the 2/undefined column. Following the last byte, the values in the SONET/SDH fault and performance monitor registers (registers 010h to 019h) are sent out, in the order they are shown in the register map, most significant byte first. The rate of the FPGA interface is 19.44 MHz for STS-12/STM-4 and STS-48/STM-16 and 1.62 MHz for STS-3/STM-1. The frequency increases by the FEC encode bandwidth expansion if FEC encode is ON.

The Overhead Extract State Machine arbitrates access to the RX_OH memories between the FPGA port and the MPC860, giving the FPGA priority. If both the microprocessor and the FPGA port request a read, the processor's read will be delayed until the FPGA read is complete. If no FPGA is present (indicated by the FPGASEL signal being inactive), then the processor interface has exclusive read access of the RX_OH memories.

After all of the receive data and overhead has been monitored and read, the transmit blocks may modify or overwrite the data. With respect to framing and Section BIP-8, the user may request that errors in the framing bytes, A1 and A2, be corrected to improve the chances that downstream devices will be able to frame to the signal. Touching the framing bytes will affect the section BIP-8 so that if they are corrected, the B1 byte will be recalculated.

Changes in any of the other overhead bytes or in the data will force this block to recalculate the B1 for all subsequent frames regardless of the state of FIXSOH. Section BIP-8 is calculated over the entire scrambled STS-N/STM-M to frame, after the overhead has been modified, and inserted into the B1 byte location of the next frame before going through the scrambling process.

With respect to Section Trace, if the ‘Send J0 Msg’ register bit is enabled, the Section Trace block will repeatedly send out, one byte per frame, the data which was written into the ‘Transmit Section Trace Memory’. The message length (1,16 or 64 bytes) is set in the section trace register and is the same for both transmit and receive messages.

Individual B2 BIP-8s are calculated over all of the bytes, with the exception of the section overhead, for each STS-1 in the previous STS-N/STM-M frame before scrambling and after any overhead byte insertions or modifications. They are supplied to the Overhead Multiplexer in the appropriate B2 locations of the current frame before scrambling. The multiplexer checks the various enable signals to decide whether to accept the B2s for insertion or keep the received B2s.

The overhead multiplexer block overwrites the received A1, A2 and B1 with the fixed framing bytes and recalculated B1 if the FIXSOH, Fix Section Overhead, feature has been requested. It also accepts the recalculated B1 if any changes to overhead or data are being or have been made by any of the other transmit blocks. If the Micro Present byte is active and transmit section trace enabled, the multiplexer will overwrite the received J0 byte with the byte from the ‘Transmit Section Trace Memory’. B2 bytes are taken from the Line BIP-8 block rather than the receive stream if (a) B2 re-calculation has been enabled, or, regardless of the enable, if (b) any of the line overhead or data bytes are being or have been changed by up stream blocks within the S3062. The enable for B2 re-calculation comes from the FIXB2 I/O signal if the processor's Micro Present byte is inactive, or from a register control bit.

The parallelizer block brings serial orderwire (E1 and E2) and data communication channels (DCCs) into the chip and organizes them into byte format to be inserted into the transmit data stream. It generates frame pulses for the orderwire and gapped 9.72 MHz clocks for all the input serial streams. The 9.72 MHz frequency increases by the FEC encode bandwidth expansion if the FEC encoder is activated. It uses the enables provided for each stream to determine whether or not to overwrite the orderwire and DCC with the received data. If the processor is activated, the enable I/Os are ORed with the software enables so that either hardware or software can control the data insertion.

If the FPGASEL pin is selecting the FPGA, the Overhead Insert State Machine block generates a frame pulse to the FPGA and a 19.44 MHz clock for STS-12/STM-4 or STS-48/STM-16 and a 1.62 MHz clock for STS-3/STM-1 rate data. This block receives 8-bit wide overhead data bytes and overhead enables from the FPGA. If permitted, the block then writes the data into the Transmit Overhead Memory (TX_OH) and writes the enables into the ‘Overhead Insert Control Memory’ (OIC).

To get permission to write the FPGA data and enables into memory, the block checks the Micro Present byte. If the byte is not active, the FPGA data is written into the TX_OH and the FPGA enables are written into the OIC. If the Micro Present byte is active, the FPGA enables are completely ignored and the block checks the ‘Transmit Access Control Memory’ to see whether or not the FPGA data should be written into the TX_OH.

The Overhead Insert State Machine block must also take care of arbitrating the timing of accesses to the TX_OH. FPGA accesses have priority over processor accesses, which are held off until the FPGA is done. This can add a wait state to the processor access. Also, the TX_OH is divided into two pages, just like the RX_OH. This block ensures that the write and read address are directed to the correct pages.

Similarly to the Overhead Extract State Machine and Receive FPGA Interface, this block runs and produces signals for the FPGA interface even during LOS and LOF (given that the FPGASEL signal is active).

The Transmit Overhead Memory is composed of two pages just like the RX_OH. While one page is being written, either from the FPGA or the microprocessor, the other page is being read and the data sent to the Overhead Insert Multiplexer. The pages are swapped at the beginning of every frame. There is a delay between writing an overhead byte and having it inserted into the data stream is important. With the two-page scheme, there is a guaranteed frame delay.

Software must also take the 2 pages into account if it wants to write an overhead byte and have it transmitted in multiple frames. For example, suppose software is running a protection exercise and wishes to change the value in the K1 byte to “exercise” (4 in the most significant nibble). It wishes to keep this value for the duration of the test, which takes several frames. It must write 4 into K1 in one page, then wait for the frame pulse to indicate that the frames have swapped, and write 4 into the second. Once that is done, it writes a ‘1’ to the OIC to enable the value to go out. For every frame thereafter, K1 will be replaced with 4. Suppose the test is done and software changes the value to 0, but it only writes the 0 in one of the 2 pages. Then the K1 being sent out will be 0 in the first frame, 4 in the second, 0 in the third, 4 in the fourth, etc. as the pages swap with each other. This will certainly cause problems for downstream devices. If software cannot guarantee that it will be able to write both pages within a few frames of each other, it should probably disable the byte insertion (write ‘0’ to the OIC enable bit) before making any TX_OH change and only re-enable the insertion after both pages match.

The contents of the ‘Transmit Access Control Memory’ determines whether a given overhead byte location in the TX_OH memory is written via the FPGA port, or from the processor interface. This memory contains 1296 (STS-48×27) single bit enables, organized as 81 words×16 bits. Each bit controls processor/FPGA access to one overhead byte location in the TX_OH memory. A logic “1” in a given bit indicates that the corresponding overhead byte location in the TX_OH memory can only be written to by the processor. Any data bound for this location from the FPGA will be ignored. A logic “0” in a given bit indicates that only the FPGA data can be written into the corresponding TX_OH memory byte. Accesses from the processor will be prevented.

The contents of this memory will only function in the manner described above if a processor is actually present, as indicated by the Micro Present byte being active. If this byte is not active, then the contents of the ‘Transmit Access Control Memory’ will be ignored, and the TX_OH memory will be written exclusively from the FPGA port. The ‘Transmit Access Control Memory’ itself is exclusively accessible from the processor interface.

The ‘Overhead Insert Control Memory’ contains 1296 (STS-48×27) single bit enables, organized as 81 words×16 bits. Each bit controls whether or not an overhead byte which is stored in the TX_OH memory will be inserted into the transmit data stream, overwriting the received byte. The OIC memory has two ports, one read-only port on which the insert enables are read out and sent to control the Overhead Insert Multiplexer, and one read/write port which is written, either via the FPGA port, or from the processor interface. If the Micro Present byte is active, then only the processor will be allowed 16-bit read/write access to this memory, even if an FPGA is also present. If the Micro Present byte is NOT active, then the FPGA will write this memory. Each overhead byte received from the FPGA is accompanied by a TX_OH_INS signal, which is the enable for that byte. These single-bit enables are accumulated into 16-bit words and written into the ‘Overhead Insertion Control Memory’. The Overhead Insert State Machine controls the sequencing of these operations.

The Overhead Insert Multiplexer block uses the enables generated from the OIC to determine whether the received data must be passed through or replaced by data from the TX_OH. If the OIC does not enable TX_OH data, and the FPGASEL signal is inactive, the block checks the enables from the Parallelizer block to determine if data from there should replace the received data. In any case, if any data is being inserted, this block signals the Section BIP-8 block to re-generate the B1. If any data other than the section overhead is being inserted, the block signals the Line BIP-8 block to re-generate B2.

This block also handles the special insertion of B1 and B2. If these bytes are enabled to come from the TX_OH, the user can request that the TX_OH value be inserted directly into the data stream or be XORed with the actual BI or B2 value. If the Micro Present byte is not active, the XORBIP pin controls this choice; otherwise, a register bit controls it. If the B1 and B2 are not enabled to come from the TX_OH, this multiplexer will not touch them. They will have been passed through or inserted correctly by the Overhead Multiplexer and will pass through this multiplexer with the data.

There are global controls to disable insertion of overhead from the TX_OH memory regardless of the contents of the OIC. If the Micro Present byte is not activated, this control comes from the MEMOH I/O signal; otherwise it comes from the ‘Insert OH’ register bit. Because the OIC is not reset to a default state, one of these signals must be activated if neither processor nor FPGA are present, or if the OIC has not been written.

After getting through the Overhead Insert Multiplexer, the data passes on to the line AIS Multiplexer #2. The first line AIS multiplexer blocked bad data from getting through to the line overhead blocks in the presence of LOS or LOF as required by standards. This multiplexer repeats the process on any newly generated overhead and allows the user to force an AIS. Thus, if LOS or LOF has been detected, or line AIS is being forced, all but the section overhead bytes will be replaced with is. The user has two ways to request automatic AIS insertion: either through the AUTOAIS I/O pin or, if the Micro Present byte has been written, through the ‘AUTOAIS’ register bit. Similarly, the user can request the line AIS forced through the DATAAIS signal pin or the ‘Force AIS’ register bit.

After going through the line AIS Multiplexer, the data is optionally scrambled with the frame synchronous SONET scrambler. The scrambler is used to guarantee that the bit pattern does not have a long sequence of 1s or 0s in it. The generating polynomial is: 1+x⁶+x⁷. It is reset to “1111111” on the most significant bit of the byte following the last byte of the first row (last Z0 byte) of the STS-N/STM-M section overhead. This bit and all subsequent bits to be scrambled are added modulo 2 to the output from the X⁷ position of the scrambler, which runs continuously throughout the complete STS-N/STM-M frame stopping at the first bit of A1. The A1, A2, and J0/Z0 bytes are not scrambled. A set of signals from the frame counter control when the scrambler is ON, OFF, or reset.

After scrambling, the data arrives at the data off multiplexer block. The multiplexer chooses between the data and all-zeros according to either the state of the DATAOFF signal if the Micro Present byte is not active or the ‘Force LOS’ register bit. Finally, the data runs through the Pass-Through MUX 300, FEC Encoder 70 and lastly the 2:1 MUX 80 (FIG. 4a) before exiting the chip. Note that all encoding happens after the all-zero multiplexer. The result of encoding all-zero data is the FSB followed by the all-zero data followed by non-zero parity bytes.

For testing purposes, the S3062 may be used to generate valid transport overhead for SONET/SDH. The input clocks (CLKINP/N and TXCLKP/N) must be supplied and FIXSOH, FIXB2, and AUTOAIS must be selected either through software or hardware. Overhead insertion from the TX_OH memory must also be OFF for the A1, A2, B1 and B2 bytes. The output will be SONET/SDH frames showing line AIS. The correct J0, E1 and section DCC bytes may also be generated through software or hardware if desired.

The processor interface operates, synchronously, as a slave to a microprocessor, such as the MPC860 Communications Controller with a maximum bus speed of 50 MHz. Access to the S3062 registers is provided for the purposes of OAM&P (operations, administration, maintenance, and provisioning). All S3062 registers, including the overhead memories, are addressed as 16-bit entities by the MPC860. All memories can be accessed with both normal, single beat, as well as burst cycle transfers. Registers, however, can only be accessed one address at a time. Since the MPC860 will always be accessing registers on the S3062 as 16-bit words, then the least significant bit of MPC860 address bus (used to address byte-wide registers), will not be connected.

The synchronous, 8-word, burst mode of operation can be used in order to achieve the required<48 ns cycle times (125 us/(1296 reads+1296 writes)) for access of all of the receive, and transmit overhead bytes within a frame time. All burst accesses must be synchronized to the frame pulse signal (FPOUTB) to insure that all bytes are extracted from a single frame, and all bytes are inserted into a single frame.

Non-burst (normal single beat) access of the section trace, RX_OH, and TX_OH Memories is also provided via the MPC860 interface. For the purpose of arbitration, the FPGA (if present) will have priority over the MPC860 (if present) in gaining access to the Overhead Data Memories. Access of the ‘Transmit Overhead Data Memory’ (TX_OH) is further restricted by the enables contained in the ‘Transmit Access Control Memory’, as described in the TAC description.

The S3062's processor transfer acknowledge signal (PTA) is re-timed internally with the transmit clock (TXCLKP/N) for all accesses except the Special Clock-Independent registers. If the transmit clock fails, a processor access of any location, other than Special Clock-Independent registers, will result in a bus error. Not all of the S3062 registers are independent of the receive clock (CLKINP/N). The receive clock and the transmit clock are required to access the FEC decode registers.

Bus errors will also occur if the processor accesses registers/memories that do not exist, belong to an unselected mode or if the processor attempts to access any registers in burst mode. The Section Trace, TX_OH, RX_OH, OIC and TAC memories are accessible in burst mode.

With respect to register map details: SONET/SDH Status Registers for Failures, Alarms, PMs, and Validated Bytes. Software can read the values of the status registers for failures, alarms, PMs and validated bytes through the processor interface.

There are two type of interrupts shown in the tables that follow: Those, like B1, which only activate when an error condition occurs and those, like LOS, which activate both when the error condition starts and when it ends, i.e., upon “change of state”. In the latter case, the user needs to know what the current state of the error is as well as the fact that it changed. That information is provided in the read-only “current state” bits. In all cases, ‘1’ means that the interrupt or the condition is present. Thus, if the B1 interrupt bit is ‘1’, a B1 BIP error has occurred, if the LOS change of state interrupt is a ‘1’, the LOS condition has either started or ended, if the current state of LOS is now a ‘1’, there is a Loss Of Signal error, etc.

Note that the interrupt enables are in registers 00a-00c.

TABLE 9 ADDR = 0x010: Clock and APS Failures

Note: The first read of this register may not result in the default value since states may have changed and interrupts may have arrived between the time that the chip was reset with the default value and the time that the register was read. RX Clk Intr: 1: Interrupt present: RX input clock (CLKINP/N) failed. 0: No interrupt present. TX Clk Intr: 1: Interrupt present: TX input clock (TXCLKP/N) failed. 0: No interrupt present. NOTE: If the TX clock is still not running when this register is read, a bus error will occur. In that case, read the Special Interrupt Register to see the clock failure indication. LOS State: 1: LOS has been detected and is still present. 0: LOS is NOT present. LOS Intr: 1: Interrupt present: Change of state in LOS. 0: No interrupt present. LOF State: 1: LOF has been detected and is still present. 0: LOF is NOT present. LOF Intr: 1: Interrupt present: Change of state in LOF. 0: No interrupt present. AIS State: 1: A line AIS has been detected and is still present. 0: L_AIS is NOT present. AIS Intr: 1: Interrupt present: Change of state of AIS_L. 0: No interrupt present. SF Intr: 1: Interrupt present: Signal Fail (SF). 0: No interrupt present. SD Intr: 1: Interrupt present: Signal Degrade (SD). 0: No interrupt present. Inconsistent APS State: 1: K1 is inconsistent. 0: K1 is NOT inconsistent. Inconsistent APS Intr: 1: Interrupt present: Change of state in inconsistent APS (K1) alarm. 0: No interrupt present. ***The RX and TX Clk Interrupts are also located in register 0x071 Special Interrupt Register. Each location has separate Interrupt Enables so please verify that the proper enables are setup for all interrupts. The enables for both RX Clk Intr and TX Clk Intr are contained in register 0x00A Clock Enable and APS Interrupts. New APS Intr: 1: Interrupt present: New APS (K1/K2) received. 0: No interrupt present.

TABLE 10 ADDR = 0x011: BIP-8, S1, RDI and Section Trace Failures

NOTE: The first read of this register may not result in the default value since states may have changed and interrupts may have arrived between the time that the chip was reset and the time that the register was read. B1 Intr: 1: Interrupt present: B1 BIP-8 error received. 0: Default. No interrupt present. B2 Intr: 1: Interrupt present: B2 BIP-8 error received. 0: Default. No interrupt present. Inconsistent S1 State: 1: S1 is inconsistent. No validated value has been found 8 consecutive times in 32 frames. 0: Default. S1 is NOT inconsistent. Inconsistent S1 Intr: 1: Interrupt present: Change of state of inconsistent S1 message. 0: Default. No interrupt present. Mismatch S1 State: 1: S1 is mismatched. Validated value does not match S1 expected message. 0: Default. S1 is NOT mismatched. Mismatch S1 Intr: 1: Interrupt present: Change of state of mismatched S1. 0: Default. No interrupt is present. New S1 Intr: 1: Interrupt present: A new S1 value has been validated. 0: Default. No interrupt is present. RDI State: 1: Line RDI has been detected and has not been cleared 0: Default. L_RDI is NOT present. RDI Intr: 1: Interrupt present: Change of state of RDI_L. 0: Default. No interrupt present. Inconsistent J0 State: 1: J0 is inconsistent. 0: Default. J0 is NOT inconsistent. Inconsistent J0 Intr: 1: Interrupt present: Change of state of inconsistent RX J0 message. 0: Default. No interrupt is present. Mismatch J0 State: 1: J0 is mismatched. 0: Default. J0 is NOT mismatched. Mismatch J0 Intr: 1: Interrupt present: Change of state of RX J0 message mismatch. 0: Default. No interrupt is present.

Register map details with respect to Gigabit Ethernet (GBE) Failures and Performance Monitoring Counts now follow. There are two types of interrupts shown below: Disparity, which only activates when an error condition occurs and Sync Loss, which activates both when the error condition starts and when it ends, i.e., upon “change of state”. In the latter case, the user needs to know what the current state of the error is as well as the fact that it changed. That information is provided in the read-only “current state” bits. In all cases, ‘1’ means that the interrupt or the condition is present. Thus, if the Disparity interrupt bit is ‘1’, a Disparity error has occurred, if the Sync Loss change of state interrupt is a ‘1’, the Sync Loss condition has either started or ended, if the current state of Sync Loss is now a ‘1’, there is a Sync Loss error. Note that the interrupt enables are in register 0x00C.

TABLE 11 ADDR = 0x01A: Gigabit Ethernet Failures

NOTE: the first read of this register may not result in the default value since states may have changed and interrupts may have arrived between the time that the chip was reset with the default value and the time that the register was read. Sync Loss State: 1: Synchronization has been lost. 0: Default. Synchronization has been found. Sync Loss Intr: 1: Interrupt present: Change of state of sync loss. 0: Default. No interrupt is present. Invalid Code Intr: 1: Interrupt present: Invalid code received. 0: Default. No interrupt is present. Disparity Intr: 1: Interrupt present: Parity error occurred. 0: Default. No interrupt is present.

With respect to PM Counts, note the following:

All PM counts are read-only and default to zero.

All are updated on the 1 second tick. If there is no tick, the register value will not change.

The “tick” is either the rising edge of PM_CLK or the change from 0 to 1 in bit 15 of register 000h, depending on which mode is enabled by the Micro Present byte and bit 1 of the Global Control register, address 001h

If the tick is running, the first read of this register may not result in the default value of zero since PMs may have arrived between the time the chip was reset with the default value and the time the register was read.

A discussion of the FEC interrupt register follows.

TABLE 12 ADDR = 0x071: Special Interrupt Register

NOTE: The first read of this register may not result in the default value since states may have changed and interrupts may have arrived between the time that the chip was reset with the default value and the time that the register was read. FEC OOF State: 1: FEC is out-of-sync. 0: FEC is NOT out-of-sync. FEC OOF Intr: 1: Interrupt present: Change of state of FEC decode out of sync. 0: No interrupt present. FIFO Intr: 1: Interrupt present: FIFO re-centering. 0: No interrupt present. RX Clock Intr: 1: Special Clock Fail interrupt present: RX input clock (CLKINP/N) failed. 0: No Special Clock Fail interrupt present. TX Clock Intr: 1: Special Clock Fail interrupt present: TX input clock (TXCLKP/N) failed. 0: No Special Clock Fail interrupt present. Reset Occurred: 1: The S3062 has been issued a software reset. 0: No S3062 reset has occurred.

Control bits are available through the processor port only. If software enables processor control by writing 59 h to the Micro Present byte, the register bits, and not the I/O pins, will affect the chip. There are three exceptions to this rule to permit both hardware and software control even when the software is present. When the Micro Present byte is activated:

Force Reset register bit will be ORed with the inverted hardware RESETB bit;

Orderwire and DCC enables will be ORed with their respective I/O enables; and

Inverted FEC disable bits will be ANDed with their respective I/O enables.

If the Micro Present byte is not programmed with a value of 59 h, control of the chip will be available on all of the I/O pins and through the registers bits that are not shared with a pin. Only the pins listed in following three tables are affected by the value of the Micro Present byte.

FIG. 18 illustrates the Micro Present Byte control MUX. An examination of FIG. 18 shows that the Micro Present byte does not affect whether or not a bit can be written. If the Micro Present byte is programmed to a value other than 59 h and the PASSTHRU pin is active, the S3062 will be in pass-through mode. When the user writes a “0” to the ‘Pass-Through’ register bit, to de-select pass-through mode, the chip will remain in pass-through mode until the user programs the Micro Present byte to the desired value of 59 h or de-selects the PASSTHRU I/O pin. Thus, the bit can be written, but it has no effect if the Micro Present byte has not been programmed with a value of 59 h. The Global control register bits and the I/O pins that provide similar functions are in the following table. All signals are active high except where noted.

TABLE 13 Shared Functions: Register Bit and I/O Pins Address Bit Bit Name Description I/O Pin 000 15  PM Tick Transfers PM counts PM_CLK to registers on low to high transition 001 6 Force Reset Forces a chip reset. RESETB When active low the pin resets the S3062, conversely, the bit clears a softward reset. 001 5 Pass-Through Enable pass-through PASSTHRU mode. 001 4/3 Rate Select Selects the data rate. RATESEL[1:0] Bit selection corresponds to specific data rate. 001 2 Force LOS Forces SONET/SDH DATAOFF block output to all zeros. 001 1 PM Tick ON Enable for PM Tick. Related to PM_CLK 001 0 Insert OH Allows the selected MEMOH bits in the OIC to determine which bytes from memory are inserted into the outgoing data stream.

The NET/SDH control register bits and the I/O pins that provide similar functions are in the continuation of Table 13. All signals are active high except where noted.

Address Bit Bit Name Description I/O Pin 002 9 Descr_OFF Enables the SONET/SDH descrambler. When active high DESCRBEN the pin enables the descrambler, conversely, the bit disables the descrambler. 002 8 Block B1s Count erred B1s (bit 8) and B2s (bit 7) by block. This means BLOCKBIP 7 Block B2s that if 6 errors occur in one byte, only 1 error is counted. A block is defined here as one byte. 003 11 Scrmbl OFF Enables the SONET/SDH scrambler. When active high the SCRBEN pin enables the scrambler, conversely, the bit disables the scrambler. 003 10 Don't Fix SOH Enables section overhead correction (A1, A2, B1). When high the pin fixes SOH while the bit does not fix SOH. 003 9 XOR B1 XOR inserted B1 values from the TX_OH with the XORBIP 4 XOR B2 regenerated B1s. XOR inserted B2 values from the TX_OH with the regenerated B2s. 003 7 E1 ON Enables the section orderwire to be inserted into the data TX_SOW_SEL stream from the external serial input pin, TX_SOW. 003 6 SDCC ON Enables the section DCC to be inserted into the data stream TX_SDCC_SEL from the external serial input pin, TX_SDCC 003 5 Fix B2 Recalculates the transmitted line BIP-8 (B2) byte FIXB2 003 3 E2 ON Enables the line orderwire to be inserted into the data stream TX_LOW_SEL from the external serial input pin, TX_LOW. 003 2 LDCC ON Enables the line DCC to be inserted into the datta stream TX_LDCC_SEL from the external serial input pin, TX_LDCC 003 1 Auto AIS Automatically sends an AIS downstream upon the detection AUTOAIS of a LOS or LOF. 003 0 Force AIS Forces a line AIS to downstream devices after SONET/SDH DATAAIS monitoring and overhead insertion.

The FEC control register bits and the I/O pins that provide similar functions are listed in the continuation of Table 13. All signals are active high except where noted.

Address Bit Bit Name Description I/O Pin 02B 3 FEC Encode Enables FEC encoding. FEC_ENC OFF When active high the pin enables FEC encoding, conversely, the register bit disables FEC encoding. 02B 2 FEC Decode Enables FEC decoding. FEC_DEC OFF When active high the pin enables FEC decoding, conversely, the register bit disables FEC decoding.

TABLE 14 Shared Functions: Register Bit and I/O Pins Address Bit Bit Name Description I/O Pin 000 15  PM Tick Transfers PM counts to registers on low to high PM_CLK transition 001 6 Force Reset Forces a chip reset. When active low the pin RESETB resets the S3062, conversely, the bit clears a software reset. 001 5 Pass-Through Enable pass-through mode. PASSTHRU 001 4-3 Rate Select Selects the data rate. Bit selection corresponds RATESEL[1:0] to specific data rate. 001 2 Force LOS Forces SONET/SDH block output to all zeros. DATAOFF 001 1 PM Tick ON Enable for PM Tick. Related to PM_CLK 001 0 Insert OH Allows the selected bits in the OIC to MEMOH determine which bytes from memory are inserted into the outgoing data stream.

Registers for performance monitoring (PM) bits and counts are described below. All PM bits and counts are read-only and default to zero. They are updated on the i second tick. If there is no tick, the register value will not change. The “tick” is either the rising edge of the PM_CLK or the change from 0 to 1 in bit 15 of register 001h, depending on which mode is enabled by the Micro Present byte and bit 1 of the Global Control register, address 001h.

TABLE 15 ADDR = 0x012: PM Register

These bits are set if the corresponding failures occurred since the last 1 second tick.

See GR-253 sections 6.2.2.3 and 6.2.2.4 for full descriptions of SONET/SDH PMs. Note that the J0 PMs are not defined in the SONET/SDH standards yet.

TABLE 16 ADDR = 0x013: B1 Error PM Count

Contains the B1 error count.

TABLE 17 ADDR = 0x014-0x15: B2 Error PM Count

Contains the B2 error count.

TABLE 18 ADDR = 0x016-0x17: REI_L PM Count

Contains the REI_L count.

Validated Bytes

If a new value is of K1/KS or S1 is found and consecutively repeated (3 times for K1/K2 and 8 times for Si) the new value will be stored in the Validated Registers for software to read.

The first read of these registers will likely result in the actual validated values rather than the default value.

TABLE 19 ADDR = 0x018: Validated K1/K2 Value

Contains the validated K1 and K2 bytes.

TABLE 20 ADDR = 0x019: Validated S1 Value

Contains the validated S1 synchronization byte.

TABLE 21 ADDR = 0x01B: Gigabit Ethernet Invalid Code Word PM Count

Contains the number of GBE Invalid Code Words that were detected.

TABLE 22 ADDR = 0x01C: Gigabit Ethernet Disparity Error PM Count

Contains the number of GBE Disparity Errors that were detected.

TABLE 23 ADDR = 0x01D: Gigabit Ethernet Sync Loss PM Count

This is a count of the transitions from in-sync to out-of-sync.

TABLE 24 ADDR = 0x01E: Combined Gigabit Ethernet PM Count

The invalid-code and disparity errors are ORed together and the resultant error is counted.

TABLE 25 ADDR = 0x030-0x031: Corrected Ones Count

Contains the number of ones that were corrected by the FEC block.

TABLE 26 ADDR = 0x032-0x033: Corrected Zeros Count

Contains the number of zeros that were corrected by the FEC block.

TABLE 27 ADDR = 0x034-0x035: Total Corrected Bits Count

Contains the total number of bits that were corrected by the FEC block.

TABLE 28 ADDR = 0x036-0x037: Total Corrected Bytes Count

Contains the total number of bytes that were corrected by the FEC block.

TABLE 29 ADDR = 0x038-0x039: Uncorrectable 255-Byte Block Count

Contains the total number of uncorrectable bytes that were detected by the FEC block.

TABLE 30 ADDR = 0x080-0x09F: Expected Section Trace Message

Contains the expected section trace message that was programmed via software.

TABLE 31 ADDR = 0x0A0-0x0BF: Received Section Trace Message

If there is a mismatch interrupt showing, this memory will contain the mismatched message. If there are no errors showing, this memory will show the expected message (unless a power-up reset has just occurred). If there is an inconsistent interrupt showing, this memory will contain the last valid message, or, if no valid messages have been received since the last reset, random data.

TABLE 32 ADDR = 0x0C0-0x0DF: Transmit Section Trace Message

Contains the section trace message to be transmitted that was programmed via software.

A system and method for creating an auxiliary data link embedded in the context of the S3062 integrated circuit have been presented above. However, the principles the invention are not limited to use in a monolithic device. Neither are the principles limited to the specific design choices and implementations of the S3062. Other embodiments and variations of the present invention will occur to those skilled in the art. 

What is claimed is:
 1. A method for generating an auxiliary communication link, the method comprising: receiving a first stream of information containing at least a first message and a second message; creating a first frame structure including a selectable first group of overhead bits and a selectable second group of overhead bits; selecting the first group of overhead bits to read; in response to reading the first group of overhead bits, synchronizing the first stream of information into the first frame structure; selecting the second group of overhead bits to read; in response to reading the second group of overhead bits, recovering the second message selecting the second group of overhead bits to read; in response to reading the second group of overhead bits, recovering the second message; and recovering the first message; in which the synchronization of the first stream of information into the first frame structure includes: organizing the first stream of information into a block with a header section having a plurality of m bits and a data section having a plurality of p bytes; reading the first group of overhead bits from the header section; in which the recovery of the second message includes reading the second group of bits in the header section; and in which the recovery of the first message includes reading bytes in the data section.
 2. The method of claim 1 in which the reception of the first stream of information includes receiving the information stream at a plurality of data rates.
 3. The method of claim 1 further comprising: deinterleaving the first stream of information into a plurality of n parallel data streams; and and in which the synchronization of the first stream of information into the first frame structure includes forming a header and a data section in each of the n parallel data stream.
 4. The method of claim 3 in which the synchronization of the first information stream into the first frame structure of n parallel data streams includes forming a combined header section of n×(m/8) bytes.
 5. The method of claim 4 which the selection of the second group of overhead bits includes selecting the number of second overhead group bits, in the range from zero to m bits, for each of the header sections of the n parallel data streams.
 6. The method of claim 5 in which the selection of the second group of overhead bits includes selecting locations for the second group of overhead bits in each of the header sections of the n parallel data stream.
 7. The method of claim 1 in which the selection of the first group of overhead bits includes selecting a plurality of q overhead bits in the range from zero to m bits.
 8. The method of claim 7 in which the selection of the second group of overhead bits includes selecting a plurality of r bits in the range from zero to m bits.
 9. The method of claim 8 in which the selection of the second group of overhead bits includes selecting the location of the second group of overhead bits in the m bits of the header section.
 10. The method of claim 8 further comprising: providing a fourth message; organizing a second stream of information into the first frame structure including a block with a header section and a data section; writing the fourth message in the header section of the second information stream; and transmitting the second stream of information.
 11. The method of claim 10 further comprising: providing a third message; and writing the third message to the data section of the second information stream.
 12. The method of claim 11 in which the provision of the third message includes providing the third message in a third stream of information having a first protocol; and in which the writing of the third message in the data section includes writing the third message independent of the first protocol.
 13. The method of claim 10 further comprising; selecting a third group of overhead bits for synchronization of the second stream of information; selecting a fourth group of overhead bits to communicate the fourth message; and in which the writing of the fourth message into the header section includes writing the third and fourth group of overhead bits into the header section of the second stream of information.
 14. The method of claims 13 in which the selection of the fourth group of overhead bits includes selecting a plurality of r overhead bits in the range from zero to m bits, and in which the selection of the fourth group of overhead bits includes selecting the location of the r overhead bits in the header section.
 15. The method of claim 13 in which the selection of the third group of overhead bits includes selecting a plurality of q overhead bits in the range from zero to m bits, and in which the selection of the third group of overhead bits includes selecting the location of the q overhead bits in the header section.
 16. The method of claim 13 in which the organization of the second stream of information into the first frame structure includes forming a header and a data section in n parallel data streams; and further comprising: interleaving the n parallel data streams into the second stream of information.
 17. The method of claim 16 in which the provision of the fourth message includes using the second message, recovered from the first stream of information, as the fourth message.
 18. The method of claim 17 in which the selection of the second group of overhead bits includes selecting a first number of bits in a first location in the header section; and in which the selection of the fourth group of overhead bits includes selecting the first number of bits in a second location in the header section.
 19. The method of claim 18 wherein a first and second repeater are provided, and in which the transmission of the second stream of information includes transmitting the second information stream from a first repeater; and further comprising: receiving the second stream of digital information at a second repeater; using the third group of overhead bits, synchronizing the second stream of information into the first frame structure; and recovering the fourth message.
 20. An integrated circuit (IC) transmission repeater with auxiliary data link, the repeater comprising: a decoder having a first input for receiving a first stream of information including a first message and a second message written in a second group of selectable overhead bits; the decoder for reading a first group of selectable overhead bits to synchronize the first stream of information into a first frame structure including a block with a data section and a header section, the decoder having a second input for selecting the first group of overhead bits or the second group of overhead bits; the decoder for reading the data section to recover the first message; the decoder for reading the second group of overhead bits to recover the second message: the decoder having a first output for providing the second message; the decoder having a second output for providing the first message; in which the decoder's synchronization of the first stream of information into the first frame structure includes the header section having a plurality of m bits and a data section having a plurality of p bytes, and in which the decoder reads the first and second group of overhead bits from the header section.
 21. The repeater of claim 20 in which the decoder receives the first stream of information at a plurality of data rates.
 22. The repeater of claim 20 further comprising: a deinterleaver circuit having an input to accept the first stream of information, the deinterleaver having a plurality of n outputs to provide the first stream of information deinterleaved into a plurality of n parallel data streams; and and in which the decoder first input is a plurality of n inputs to accept the plurality of n parallel data streams from the deinterleaver circuit, the decoder reads the first group of overhead bits from the n parallel header sections to synchronize the first stream of information, and in which the decoder reads the second group of overhead bits from n parallel header sections to recover the second message.
 23. The repeater of claims 22 in which the decoder second input accepts commands to select the number of second group overhead bits, in the range from zero to m bits, for each of the header sections of the n parallel data streams, and the locations for the second group of overhead bits in each of the header sections of the n parallel data stream header sections.
 24. The repeater of claim 23 further comprising: an encoder having a first input to accept a fourth message, the encoder organizing a second stream of information into the first frame structure including block with a header section and a data section, the encoder having an output to supply the fourth message written in the fourth group of overhead bits of the header section.
 25. The repeater of claim 24 in which the encoder has a second input for selecting a third group of overhead bits for synchronization of the second stream of information, and in which the encoder writes the third group of overhead bits in the header section.
 26. The repeater of claim 25 in which the encoder accepts a third message, the encoder writing the third message in the data section of the first frame structure.
 27. The repeater of claim 26 in which the encoder receives the third message in a third stream of information having a first communication protocol, and in which the encoder writes the third message in the data section independent of the first protocol.
 28. The repeater of claim 25 in which the encoder second input accepts commands to select a plurality of r fourth group overhead bits in the range from zero to m bits, and in which the selection of the fourth group of overhead bits includes selecting a second location in the header section.
 29. The repeater of claim 28 in which the encoder includes a plurality of n outputs to provide a plurality of n parallel data streams organized in the first frame structure including n blocks having header and data sections, in which the encoder second input accepts commands for selecting the number of fourth group overhead bits in the range from zero to m bits, in each of the n header sections, and in which the selection of the fourth group of overhead bits includes selecting a second location in each of the n header sections; and further comprising: an interleaver having a plurality of n inputs connected to the plurality of n encoder outputs, the interleaver interleaving the n parallel data streams to form the second stream of information at the interleaver output.
 30. The repeater of claim 28 in which the decoder's second input accepts commands for selecting a first number of second group overhead bits in a first location in the header section; in which first output of the repeater is connected to the encoder first input to provide the fourth message, so that the second message is passed through as the fourth message; and in which the encoder's second input accepts commands for selecting the first number of fourth group overhead bits in a second location in the header section.
 31. The repeater of claim 20 in which decoder second input accepts commands to select the first group of overhead bits from a plurality of q overhead bits in the range from zero to m bits.
 32. The repeater of claim 31 in which the decoder second input accepts commands to select the second group of overhead bits from a plurality of r overhead bits in the range from zero to m bits.
 33. The repeater of claim 32 in which the decoder second input accepts commands to select a first location for the second group of overhead bits in the header section. 